<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Rv6xx dpm problems"
href="https://bugs.freedesktop.org/show_bug.cgi?id=66963#c283">Comment # 283</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 <span class="vcard"><a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to Kajzer from <a href="show_bug.cgi?id=66963#c282">comment #282</a>)
<span class="quote">> 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</span >
You only need this if you had previously started a bisect (git bisect start).
<span class="quote">> $ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13</span >
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).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>