http://bugs.winehq.org/show_bug.cgi?id=10601 --- Comment #37 from Dan Kegel <dank(a)kegel.com> 2009-10-09 15:15:47 --- I don't know if the log is helpful, it may well be. Knowing which patch broke something is a pretty powerful signal, though, and kind of trumps logs if it's available. http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html says: -- snip -- If you have a script that can tell if the current source code is good or bad, you can bisect by issuing the command: $ git bisect run my_script arguments Note that the script (my_script in the above example) should exit with code 0 if the current source code is good, and exit with a code between 1 and 127 (inclusive), except 125, if the current source code is bad. -- snip -- So potentially a script like rm -rf ~/.wine exec sh winetricks -q nocrashdialog dotnet20 would work as an argument to git bisect run. I haven't verified whether the exit status is set properly, though. One always has to tread carefully when using tools like this, of course. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.