On Wed, 7 Dec 2011, Jeff King wrote: > On Wed, Dec 07, 2011 at 07:18:13PM -0500, Nicolas Pitre wrote: > > > I certainly never did a multi-ref fetch myself. > > Not consciously, perhaps, but you do it all the time without realizing > it: > > $ git clone git://git.kernel.org/pub/scm/git/git.git > $ cd git > $ git fetch -v origin > = [up to date] maint -> origin/maint > = [up to date] master -> origin/master > = [up to date] next -> origin/next > = [up to date] pu -> origin/pu > = [up to date] todo -> origin/todo > $ cat .git/FETCH_HEAD > b1af9630d758e1728fc0008b3f18d90d8f87f4c5 not-for-merge branch 'maint' of git://git.kernel.org/pub/scm/git/git > 4cb5d10b14dcbe0155bed9c45ccb94e83bd4c599 branch 'master' of git://git.kernel.org/pub/scm/git/git > 03e5527c5df33d4550ccc1446d861c0aa5689d58 not-for-merge branch 'next' of git://git.kernel.org/pub/scm/git/git > cc4e3f01fc6a5e09ae5bbdc464965981fae4cf39 not-for-merge branch 'pu' of git://git.kernel.org/pub/scm/git/git > 7a02dba15bd28826344f9c14a5e2b5c57eeb7e50 not-for-merge branch 'todo' of git://git.kernel.org/pub/scm/git/git OK, nevermind. I admitedly never have been close enough to the related code. And I don't think this particular case is interesting anyway as the reflogs for the various branches alre already involved. I was thinking more about the "git fetch git://some.random.repo foobar" case where the summary also explicitly shows: From: git://some.random.repo ...... foobar -> FETCH_HEAD In that case the only reference to the fetched branch is stored in FETCH_HEAD and that is what might be worthwile for a reflog. Nicolas -- 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