Re: [RFC] Fourth round of support for cloning submodules
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- May 25, 2007, 14:54 UTC
- Message-ID
- <Pine.LNX.4.64.0705251553190.4648@racer.site>
- In-Reply-To
- <200705251651.35234.Josef.Weidendorfer@gmx.de>
Hi,
On Fri, 25 May 2007, Josef Weidendorfer wrote:
Show 16 quoted lines
> On Friday 25 May 2007, Johannes Schindelin wrote: > > On Fri, 25 May 2007, Josef Weidendorfer wrote: > > > > > * Submodules can appear/disappear any time in the superproject. > > > Therefore, going back in time can make it necessary to have to clone > > > a submodule you did not have before. > > > > > > * Not every submodule is interesting for every developer; therefore, > > > an important design-decision for submodules is to allow at git-clone > > > time to not clone some submodules at all. However, you can change > > > your mind and want to follow a given submodule later. > > > > Okay, so there are exceptions to the rule, just as everywhere. > > The question here is in how many superprojects the exception will become > the rule, which would make manual overriding quite cumbersome.
I never disputed that manual overriding is cumbersome. However, I dispute that automatic overriding is _possible_.
> I agree with Junio that a simply, basic and robust submodule > implementation currently is important as first goal.
Good. Me, too.
Ciao, Dscho