http://bugs.winehq.org/show_bug.cgi?id=13832
--- Comment #11 from OlekA brodo@o2.pl 2008-06-26 06:17:10 ---
"0 revisions left to test after this" means no more revisions left *after* current one. Therefore you need to test your application once more (that is, one more git-bisect good/bad step is necessary).
BTW, in Regression Testing guide ( http://wiki.winehq.org/RegressionTesting ) in the "Testing the Actual Program" section you can find big notice specific to this message:
"If you see: Bisecting: 0 revisions left to test after this
THEN YOU ARE NOT DONE YET!"
Yes, I recompiled it again and got this:
olek@linux:~/wine-git$ git bisect bad 4b53154f361b9fdc504be5e099e84c6686f940fe is first bad commit commit 4b53154f361b9fdc504be5e099e84c6686f940fe Author: Detlef Riekenberg wine.dev@web.de Date: Thu Jul 26 23:05:27 2007 +0200
winspool: Return the full path for the driver.
:040000 040000 696dbd0389c83249ca54aa4b228360a348f14088 8825f509c1d92b07c610ac1c79f63cbb3748dc2d M dlls
olek@linux:~/wine-git$ ./wine --version wine-0.9.41-393-g4b53154
what can I do next (if any) ? Bug 13832 is already opened...