From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sun, 17 Feb 2008 23:27:04 GMT
Subject: Re: Intoducing the .git file (again)
Message-ID: <alpine.LSU.1.00.0802172324520.30505@racer.site>
In-Reply-To: <8c5c35580802171429m1091492dgd65e13c94de08bd4@mail.gmail.com>

Hi,

On Sun, 17 Feb 2008, Lars Hjemli wrote:

> On Feb 17, 2008 11:20 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>
> > On Sun, 17 Feb 2008, Lars Hjemli wrote:
> >
> > > PPS: If included, the .git file should probably be used by 
> > > git-submodule to clone submodule repositories into something like 
> > > $GIT_DIR/submodules/<name>, as that would make local submodule 
> > > changes more resistant to dataloss due to checkout/reset in the 
> > > containing repository.
> >
> > I don't buy that argument.  For the moment, the submodules are 
> > self-contained repositories.  The superproject does not even have to 
> > have a single object contained in a submodule.  I'd try to keep that 
> > separation.
> 
> They would still be separated and self-contained repositories, but with 
> my suggestion the submodule repository would be moved out of the working 
> tree of the containing repository. Which I believe is a good thing, 
> especially when you switch from one branch in the containing repository 
> which had the submodule in './foo' to another branch where the submodule 
> is located in './lib/foo'.

That is a good argument.

But what about the argument when you stop being interested in the 
superproject, and move the submodule out of it (then deleting the 
superproject)?

However, when a submodule is deleted, wasn't the plan all along to put the 
submodule's .git/ into the superproject's .git/submodules-deleted/ or some 
such?

Ciao,
Dscho