http://bugs.winehq.org/show_bug.cgi?id=14978
--- Comment #6 from Reinhard Berger geist1@sms.at 2008-09-04 04:18:05 --- I've readed the regession page carefuly, there stays : If you see: Bisecting: 0 revisions left to test after this
THEN YOU ARE NOT DONE YET! Once that patch is identified ...
That means for the following :
After i see the 0 revisions left, i should do another start of the application.
I've done this, but it still fails (bug is still present) then issued the command "git bisect bad"
This will display me the following things :
87c3df1578803f63ce68096c07c42c3af279077c is first bad commit commit 87c3df1578803f63ce68096c07c42c3af279077c Author: Juan Lang juan.lang@gmail.com Date: Fri Jul 25 11:16:54 2008 -0700
shlwapi: Use CharNextA to iterate through characters in PathAddBackslashA. Fixes problems with MBCS paths.
:040000 040000 98c6fa7008a200d657fbc7b3e178ed819df7470f 8e641bd55bc1d6eee5b64c241c6118306ed65e5d M dlls
But i'm pretty sure that this is not the reason.
I am unable to find the patch wich is responsable for that bug, since i can't tell GIT after all that pacthes a "good" command.
Something else i could do ?