http://bugs.winehq.org/show_bug.cgi?id=13547
--- Comment #17 from Austin English austinenglish@gmail.com 2008-06-01 18:56:02 --- (In reply to comment #11)
Please explain further Austin..
There's a guide here: http://wiki.winehq.org/ReverseRegressionTesting
In short, 0.9.59 worked fine, but 1.0-rc1 is broken (crashes). But, you want to find the patch that broke the textures. You can't because of the crash. So to do so, you need to find the patch that broke the crash (which you know, it's eaea28e5d83b8d302eed62dbf574b5d6d2c14cdd). Save a copy of this patch, name it crash.diff. Then, do:
$ git bisect start $ git bisect good wine-0.9.59 $ git bisect bad wine-1.0-rc1
Here things get trickier. If the current compile is 'before' eaea28e5d83b8d302eed62dbf574b5d6d2c14cdd, then you just compile as normal. If it's 'after', then you need to revert the patch, to prevent the crash: $ patch -p1 -R < crash.diff
Then build as normal: $ ./configure && make depend && make clean && make
Before doing a git good/bad, however, you'll have to 'fix' any changes you made to the git tree, so if you reverted that patch, then reapply it: $ patch -p1 < crash.diff
Of course, if you didn't apply, ignore. Then do: $ git good or $ git bad As applicable. Lather, rinse, repeat.
Confusing, I know, but the only way to find that patch.