Hi, On Sat, 5 Jul 2008, Junio C Hamano wrote: > Sylvain Joyeux <sylvain.joyeux@xxxxxxx> writes: > > > This patch makes the output of git-submodule more useful to handle the > > management of a repository using multiple submodules. Namely, it > > displays informations about how the current checked out version relates > > to the registered one (i.e. direct parent, direct child, "just > > different", registered revision does not exist), and displays if the > > submodules contain uncommitted changes. > > > > This (among other things) allows to do git-submodule update while > > knowing exactly what will happen. > > -- > > Sylvain > > > >>>From 16553a9b210a956b0af961d55a9cf06f1b9b8114 Mon Sep 17 00:00:00 2001 > > From: Sylvain Joyeux <sylvain.joyeux@xxxxxxx> > > Date: Tue, 1 Jul 2008 16:01:01 +0200 > > Subject: [PATCH] more information in git-submodule status output > > > > This commit adds more information in the 'status' output of > > git-submodule. More specifically, it displays different flags if the > > submodule and the registered revision are direct parents (> and <, > > depending on which is the ancestor), if they are not direct parents (+) > > or if the registered revision cannot be found (i.e. if submodule update > > would fail, '!') > > > > Finally, it shows if the submodule contains uncommitted changes (M flag) > > Which one is the commit message ;-)? I think it is clear that Sylvain has not read Documentation/SubmittingPatches yet. > People who rely on working submodule support, do you have any feedback > on this patch? Not yet. Will test/comment when the spurious "fetch" is fixed. 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
