Re: [PATCH] better git-submodule status output

From: Sylvain Joyeux <sylvain.joyeux@dfki.de>
Date: Jul 8, 2008, 08:00 UTC
Message-ID: <20080708080042.GB3628@joyeux>
In-Reply-To: <7v8wwd4kvb.fsf@gitster.siamese.dyndns.org>

On Mon, Jul 07, 2008 at 11:20:08AM -0700, Junio C Hamano wrote:

Show 6 quoted lines

> > Is it possible to make 'fetch' only .. well .. fetch objects, without
> > updating any refs?
> 
> By honestly saying "The superproject binds a commit you do not have
> locally at these paths", the user *can* choose *when* to go there and
> update, or have "git submodule update" command to that for him.

Agreed. The problem is that git submodule update does not only fetches the new refs but *also* checks out the commit currently registered in the superproject. Therefore git-submodule status *and* git-submodule summary cannot tell you anything after a git-submodule update.

What I was missing is, given the current discussion, a git-submodule fetch alike to what Avery was proposing, which fetches all submodules in one command. Having to do the fetch/update manually for each submodule is really cumbersome -- I have around 30 modules in the superproject.

Sylvain