http://bugs.winehq.org/show_bug.cgi?id=20792 --- Comment #12 from Wylda <wylda(a)volny.cz> 2009-11-22 19:49:03 --- (In reply to comment #10)
You can use 'git clean' to clean out your git tree.
I tried "git clean -d -f" even with "make distclean" _before_ doing "git bisect bad" to have distclean for right version, but it did not help. Again, I missed that commit completely (862965f4f71b19f251934b11d1e998831ccbaee6 --mentioned in bug 20799). (In reply to comment #11)
If you can't keep your git tree clean (pretty hard with active development) then you should: 1. User out-of-tree building: cd wine.git mkdir ../wine.git-build cd ../wine.git-build ../wine.git/configure && make depend && make all
I like this method :) Thanks! Anyway. Is it normal to miss the GOOD commit during git bisect?? (just repeat, that during git bisect between 1.1.29 and 1.1.30 i got all BAD). -- 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.