http://bugs.winehq.org/show_bug.cgi?id=13832
L. Rahyen mail@science.su changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mail@science.su
--- Comment #10 from L. Rahyen mail@science.su 2008-06-26 05:16:42 ---
... The last output from bisect is this : ... Bisecting: 0 revisions left to test after this [4b53154f361b9fdc504be5e099e84c6686f940fe] winspool: Return the full path for the driver. ... What should I do next ?
"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!"