Hi, On Tue, 29 Jul 2008, Pierre Habouzit wrote: > On Tue, Jul 29, 2008 at 12:15:05PM +0000, Johannes Schindelin wrote: > > On Tue, 29 Jul 2008, Petr Baudis wrote: > > > On Tue, Jul 29, 2008 at 10:37:55AM +0200, Pierre Habouzit wrote: > > > > > > > path = "$path" > > > > url = git://somewhere/ > > > > tracks = master > [...] > > But then, how does the relation to the currently _committed_ state get > > displayed? > > Hmm _that's_ why you need a name for it. I do not understand. We are talking about three different things here: 1) the committed state of the submodule 2) the local state of the submodule 3) the state of the "tracks" branch We always have 1) and we have 2) _iff_ the submodule was checked out. We only will have 3) if "tracks" is set in .git/config (for consistency's sake, we should not read that information directly from the .gitmodules file, but let the user override it in .git/config after "submodule init". > Or you need the submodule to be aware he's one, and then one would have > some kind of "magic" word to name this sha1. And tools would find out in > the supermodule what it translates into. You lost me there. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
