I'm VERY excited. My wine worked for the first time in two weeks.. emulating CS. I went through ONE "git bisect bad" Code: van@vortex:~/wine-git$ git bisect bad Bisecting: 351 revisions left to test after this [1077238143911d10650eb6ee9f0fa3e269ae7eb4] cabinet: Added a test for FDICopy with an empty cabinet file. van@vortex:~/wine-git$ wine "C:\Valve\Steam\Steam.exe" van@vortex:~/wine-git$ git bisect good Bisecting: 175 revisions left to test after this [a2073f2979ea9e440247ea0503be4dce840fc782] dxerr9: Don't use Wine debugging macros in static libraries. van@vortex:~/wine-git$ Now, that I found this - and wine works, what do I do now? the guide says: > > This will reposition the source code in the middle of the remaining patches. You will then recompile Wine and test for the bug again. After a few tests, git will eventually identify the bad patch. It should look something like this: > > a460a2df43aa8eae10b1db028c6020829b009c54 is first bad commit > commit a460a2df43aa8eae10b1db028c6020829b009c54 > Author: Stefan Doesinger <stefandoesinger@xxxxxx> > Date: Sat Jun 9 14:27:41 2007 +0200 > wined3d: Store the gl information in a per adapter structure and initialize it only once. > :040000 040000 d8ae35832fcdbca8de07acae73b9e21564ced413 > 1720cc38fb598110071c9ee4f21f8f61b6f764c3 M dlls > > Note that it says: > > a460a2df43aa8eae10b1db028c6020829b009c54 is first bad commit > > If you see: > > Bisecting: 0 revisions left to test after this > > THEN YOU ARE NOT DONE YET! My git does not say anything like this above. mine said: > > van@vortex:~/wine-git$ git bisect good > Bisecting: 175 revisions left to test after this > [a2073f2979ea9e440247ea0503be4dce840fc782] dxerr9: Don't use Wine debugging macros in static libraries. > van@vortex:~/wine-git$ > > So I'm not sure what to do. Please advise. Thank you so much!
