Re: [RFC] Light-weight checkouts via ".gitlink"

From: Josef Weidendorfer <josef.weidendorfer@gmx.de>
Date: Dec 9, 2006, 01:46 UTC
Message-ID: <200612090246.20770.Josef.Weidendorfer@gmx.de>
In-Reply-To: <200612090053.48186.jnareb@gmail.com>

On Saturday 09 December 2006 00:53, Jakub Narebski wrote:

Show 17 quoted lines

> Josef Weidendorfer wrote:
> > On Friday 08 December 2006 23:54, Josef Weidendorfer wrote:
> >> Jakub Narebski wrote:
> >>> NAME = name
> > 
> > Forgot to mention in the proposal:
> > If you recursively have light-weight checkouts inside each other,
> > the real "name" (for .git/external/<name/ and for further submodule
> > configuration e.g. in .git/modules of the base repository)
> > should of course be the concatenation of the names in the .gitlink
> > files while going up to the base repository.
> 
> Why concatenation? I thought the name would be ID of submodule,
> and should be just somehow unique.
> 
> And if concatenation, pehaps some forbidden character inserted between
> them? Like '/' for example ;-)

Yes, you are right. Nesting of submodules really is an important issue. The .gitlink file allows us to put the submodule GITDIR somewhere in the supermodul's GITDIR. The idea is that you can clone the submodule GITDIR if you want. With submodule "inner" nesting inside of submodule "outer", the GITDIR of "outer" should have the GITDIR of inner inside to allow for cloning "outer" together with its submodule "inner".

So it is not enough to have a submodule "outer" and a submodule "outer/inner" in the supermodule. We want

	super.git/ext/outer.git/

to be the GITDIR for submodule "outer", and inside

	super.git/ext/outer.git/ext/inner.git
.

Actually, it would be nice if this .gitlink proposal did not have to deal with it. Instead, a .gitlink should be so flexible to allow such nesting if needed.