[Adonthell-devel] Re: git, anyone?

[Chris Frey]

On Thu, Jan 22, 2009 at 10:53:28PM +0100, Kai Sterker wrote:
> Granted, that's only the first of a number of CVS modules, but I
> wouldn't bother much about adonthell-0.3 or wastesedge, as not much
> development will happen on those. tools will be interesting though.
> Not sure about gfx, after hearing what Ingo said about large binary
> files.

I'd leave the CVS repos hanging around... always good to have backups
like that. :-)


> Which brings me to another question. How would multiple CVS modules be
> handled by git?
> I came across this thread on Savannah
> (https://savannah.gnu.org/support/?106565), which offers a way to have
> multiple modules in the repository that can be checked out
> individually, if I understand correctly. It would require Savannah
> folks to set up stuff manually, though.

If I understand that right, they just have one git repo for each
CVS module, which seems perfectly reasonable.

Indeed, with kernel develoment, Greg KH starts a new git repo for each
stable kernel series he releases.  It's just a matter of how you want
to organize things.

It *is* possible to have multiple branches in a git repo with completely
different contents.  Using Barry as shameless example again, here's
my main tree:

http://repo.or.cz/w/barry.git?a=tree;h=4ca57235d0c995605b43683f5a10283c804344ae;hb=4ca57235d0c995605b43683f5a10283c804344ae

And here's the 'scripts' branch in the same repo:

http://repo.or.cz/w/barry.git?a=tree;h=2f60c9dc18ebe0f1171dde0be8f8366e324f81e0;hb=2f60c9dc18ebe0f1171dde0be8f8366e324f81e0

Completely different trees, two branches, same git repo.

To work with them, I have two clones on my system, one with the scripts
branch always checked out so the scripts are handy.

If you can have multiple git repos in one common area, though, I think
that's a cleaner and clearer option, especially for new users wondering
how to get at the code.

- Chris