Re: git bisect goes wild?

2009/2/24 Jan Kara:

 Hi,

 I've been bisecting some change in Linux kernel. The output of
"git bisect log" is:

...

git-bisect bad 419217cb1d0266f62cbea6cdc6b1d1324350bc34

...

git-bisect good 3e9830dcabdeb3656855ec1b678b6bcf3b50261c

 But after the last command, I was sent to commit
9ec76fbf7d6da3e98070a7059699d0ca019b0c9b which is far outside the window
between the last good and bad commit.

How did you determine that this commit is outside the window?

When I run "gitk 3e9830..419217" it shows that commit, as does "git
log". 9ec76fb appears to be inside the window to me.

Peter Harris