Re: [RFC] Submodules in GIT
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Dec 1, 2006, 23:03 UTC
- Message-ID
- <200612020003.14377.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <4570AF8F.1000801@stephan-feder.de>
On Friday 01 December 2006 23:41, sf wrote:
Show 10 quoted lines
> 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. Instead fetch only the submodules you are interested in. > You do not have to fetch the whole repository.
But what, when I *want* to fetch the supermodule because of the source tree which is only available in the supermodule?
Of course, you can argue that the only objects in trees of a supermodule should be submodule commits, but this is quite restricting the usage of supermodules.
See further arguments for a submodule namespace in my other mail. You probably want to specify policies about submodule handling. This information has to be indexed by some name independent from a supermodule commit.
Josef