Re: [PATCH] better git-submodule status output

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 7, 2008, 14:37 UTC
Message-ID: <alpine.DEB.1.00.0807071537070.18205@racer>
In-Reply-To: <alpine.DEB.1.00.0807071533240.18205@racer>

Hi,

On Mon, 7 Jul 2008, Johannes Schindelin wrote:

Show 11 quoted lines

> On Mon, 7 Jul 2008, Avery Pennarun wrote:
> 
> > The trick here, I think, is that there's only one time the submodule 
> > should be linked to a commit you don't actually have.  It should only 
> > happen if your parent module (supermodule) has been updated, but you 
> > haven't recently done a fetch in the submodule.
> 
> Noooooo!
> 
> If I am actively working on the submodule, the supermodule has _no 
> business_ trying to wreck my state.

Ooops.  The part I should have quoted was this:

> Thus, I'd say the best fix would be to find a way to have "git pull" or 
> "git fetch" in the supermodule also do a fetch in the submodule.

Now you will understand my objection, hopefully, Dscho