From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Mon, 12 Jun 2006 11:41:34 GMT
Subject: bisect and gitk happy together
Message-ID: <46a038f90606120441p74dd4872y441fe04470f4acd5@mail.gmail.com>

I was using git-bisect earlier today, and at the exact point where it
told be about the bad commit, I opened gitk, which was showing all the
bad and good commits. It is great!

Two "user" notes, however:

 - git-bisect visualise wasn't as useful as just a plain gitk. (This
may be because I was working with ~60 commits in a medium-sized
project).

 - gitk didn't show the bad commit tagged specially, even if
git-bisect had just identified it. Of course I could find it, but I
had all the other good/bad commits well labelled. And not the one I
was looking for. Odd.

In any case, the bisect + gitk combo saved the day. I'm too ashamed to
tell what the bug actually was, though ;-)


martin