<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen"
href="https://bugs.freedesktop.org/show_bug.cgi?id=53926#c52">Comment # 52</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen"
href="https://bugs.freedesktop.org/show_bug.cgi?id=53926">bug 53926</a>
from <span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span></b>
<pre>Yeah, that's what I've tried to explain (but without the pretty branch graphs).
If you're sure that you haven't marked any commits wrongly with good/bad, you
can restart git bisect with the capture bisect log, i.e. after starting the
bisect ignore the first bisect request and manually mark all the already tested
commits with
$ git bisect good|bad|skip sha1
After that's done, git will compute a new optimal bisect point and check it out
for testing.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>