<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Rv6xx dpm problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=66963#c282">Comment # 282</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Rv6xx dpm problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=66963">bug 66963</a> from <a class="email" href="mailto:kap3tan@gmail.com" title="Kajzer <kap3tan@gmail.com>"> Kajzer</a> <pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=66963#c280">comment #280</a>) > You don't need to start the bisect again. `git bisect reset` will clean up > the bisect and reset your current HEAD to where it was when started the > bisect. At that point just run `git reset --hard > 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` or 'git checkout -b testing > 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` to checkout the specific commit > you want to test. The second method creates a new branch called testing > with HEAD set to the specified commit. The reset command resets the HEAD of > the current tree to the specified commit. 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 $ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13 Of course after I'm done with current test. Please correct me if I'm wrong.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>