Re: git-status for submodules
- From
- Chris Frey <cdfrey@foursquare.net>
- Date
- Nov 21, 2008, 22:42 UTC
- Message-ID
- <20081121224247.GB27049@foursquare.net>
- In-Reply-To
- <7vabbtqga8.fsf@gitster.siamese.dyndns.org>
On Fri, Nov 21, 2008 at 06:56:15AM -0800, Junio C Hamano wrote:
> My understanding is that this is exactly by design. The supermodule > tracks which commit in the subproject is bound to the tree location.
Show 7 quoted lines
> the submodule support is geared toward supporting this layout: > > - "super" has a subproject X at "sub" > > - When you do a real work on the subproject X, you do so as if > there is no supermodule. IOW, subproject X has to be able to > stand on its own.
It's true that subproject X has to be able to stand on its own. That is important from git's perspective as well as for managing subprojects in general.
But I don't see the advantage in hiding submodule information from the supermodule, and if that hiding is by design, I think the design is wrong. In order to manage the various modules effectively (actually, in order to manage any git repo effectively), you need to know what's changed, and git-status is the way to do that. I don't see why submodules should break that.
With the new submodule foreach command, though, it should be possible to add that as a config option, similar to the way submodule summary is handled now. Maybe I can cook up a patch for that.
- Chris