Re: [RFC] Submodules in GIT
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Dec 1, 2006, 23:36 UTC
- Message-ID
- <200612020036.08826.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <Pine.LNX.4.64.0612011505190.3695@woody.osdl.org>
On Saturday 02 December 2006 00:09, Linus Torvalds wrote:
Show 15 quoted lines
> > On Fri, 1 Dec 2006, sf wrote: > > Linus Torvalds wrote: > > ... > > > In contrast, a submodule that we don't fetch is an all-or-nothing > > > situation: we simply don't have the data at all, and it's really a matter > > > of simply not recursing into that submodule at all - much more like not > > > checking out a particular part of the tree. > > > > If you do not want to fetch all of the supermodule then do not fetch the > > supermodule. > > So why do you want to limit it? There's absolutely no cost to saying "I > want to see all the common shared infrastructure, but I'm actually only > interested in this one submodule that I work with".
So you are for a global submodule namespace in supermodule repositories, do I understand correctly?
Otherwise, how would you specify the submodules at clone time given the ability that submodule roots can have relative path changed arbitrarily between commits?