Comment # 283
on bug 66963
from Alex Deucher
(In reply to Kajzer from comment #282) > I'm running now on kernel compiled with first method, if previous bisect was > indeed done right I don't expect dpm freeze. > > Anyway, thanks for the second method, if I understood you correctly, > basically I can test if Michel's commit is bad or not by running : > $ git bisect reset You only need this if you had previously started a bisect (git bisect start). > $ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13 that will create a new branch named testing. If you already did that, you will need to delete the existing testing branch first before you create another branch with the same name. So either delete the branch when you are done with it (git branch -D testing) or create a new branch name (git branch -b testing2 02376d8282b88f07d0716da6155094c8760b1a13).
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
