https://bugs.freedesktop.org/show_bug.cgi?id=33867 --- Comment #7 from Alex Deucher <agd5f@xxxxxxxxx> 2011-02-05 11:29:37 PST --- When you bisect, you want to focus on only the specific bug you are tracking. If you hit some other bug or the status of the commit is indeterminate, don't mark the commit as bad, skip it (git bisect skip). Also, if you may need to have a certain patch applied all the time for testing certain things. E.g., if you get hangs without 1e644d6dce366a7bae22484f60133b61ba322911 applied, make a patch of that commit and manually re-apply it before testing each commit in the bisect. E.g., create a patch from the commit: git show 1e644d6dce366a7bae22484f60133b61ba322911 > fix.patch then before each test in the bisect, manually apply the patch: patch -p1 -i fix.patch -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
