http://bugs.winehq.org/show_bug.cgi?id=12392
--- Comment #6 from Austin English austinenglish@gmail.com 2008-04-08 01:48:25 --- (In reply to comment #5)
Then there is something wrong. Any 'git bisect good/bad' commands after this message I posted produce exactly zero output. The last command would have been 'git bisect bad'.
You should receive a message saying 'x is the first bad commit', not 'Bisecting: 0 revisions left to test after this'.