Misbehaving git bisect bad HEAD

2014-12-22 Thread Andreas Schwab
Running git bisect bad should be the same as git bisect bad HEAD, shouldn't it? When replaying this bisect log on the Linux kernel tree: git bisect start # bad: [97bf6af1f928216fd6c5a66e8a57bfa95a659672] Linux 3.19-rc1 git bisect bad 97bf6af1f928216fd6c5a66e8a57bfa95a659672 # good:

Re: Misbehaving git bisect bad HEAD

2014-12-22 Thread Christian Couder
On Mon, Dec 22, 2014 at 3:04 PM, Andreas Schwab sch...@linux-m68k.org wrote: Running git bisect bad should be the same as git bisect bad HEAD, shouldn't it? Yeah, it should. When replaying this bisect log on the Linux kernel tree: git bisect start # bad: