]> git.vanrenterghem.biz Git - git.ikiwiki.info.git/commit
Merge commit '97de9bb8605eaeb47edd4d80b444605676bb83e2' into slop
authorJoey Hess <joey@gnu.kitenet.net>
Thu, 27 Aug 2009 23:55:50 +0000 (19:55 -0400)
committerJoey Hess <joey@gnu.kitenet.net>
Thu, 27 Aug 2009 23:57:18 +0000 (19:57 -0400)
commit7399b073a794fa941a88d75a89753f72998d1913
tree9cf8713723a61a83f81929657379d0a134682e79
parent8cfba729702e52ba2b3716d7a2d2daaff61a1604
parent97de9bb8605eaeb47edd4d80b444605676bb83e2
Merge commit '97de9bb8605eaeb47edd4d80b444605676bb83e2' into slop

For some reason, when I run:

gitk $(git for-each-ref --format='%(refname)' 'refs/remotes/'; git
for-each-ref --format='^%(refname)' 'refs/heads/' 'refs/remotes/origin/'
'refs/tags/')

It shows a bunch of commits, that are present in master, along the way to
this commit, in intigreti's remote.

AFAICS, there is nothing in there that I should be considering merging, so
rather than debug why it does that, I'll just merge it into this branch.
The command above will actually notice it's merged to one of my branches
then, and will avoid cluttering the display of other, unmerged stuff with
it.

I earlier merged a few branches into this one that I had deleted, but that
are still present in other's repos, so that they also don't show up in the
above gitk.
debian/control