Re: git bisect goes wild?
- From
- Peter Harris <git@peter.is-a-geek.org>
- Date
- Feb 24, 2009, 18:59 UTC
- Message-ID
- <eaa105840902241059y70143c43s7d12b10fe35127e6@mail.gmail.com>
- In-Reply-To
- <20090224184414.GE22108@duck.suse.cz>
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
...
Show 5 quoted lines
> 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