Re: git submodules
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jul 29, 2008, 12:15 UTC
- Message-ID
- <alpine.DEB.1.00.0807291413460.4631@eeepc-johanness>
- In-Reply-To
- <20080729085125.GJ32184@machine.or.cz>
Hi,
On Tue, 29 Jul 2008, Petr Baudis wrote:
Show 12 quoted lines
> On Tue, Jul 29, 2008 at 10:37:55AM +0200, Pierre Habouzit wrote: > > > path = "$path" > > url = git://somewhere/ > > tracks = master > > I do like this (well, I'd just name it "branch" instead of "tracks"). I > use submodules very "traditionally" just to bind external projects of > certain version to my project, but I have been already thinking about > implementing this merely as a hint for others to know what branch should > the other developers follow when updating the submodule to a newer > version.
As long as you only use it in "submodule status" to say what the relation of the current revision is with respect to the "tracks" branch...
But then, how does the relation to the currently _committed_ state get displayed?
Ciao, Dscho