<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#c51">Comment # 51</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:nmschulte@gmail.com" title="Nathan Schulte <nmschulte@gmail.com>"> <span class="fn">Nathan Schulte</span></a>
</span></b>
<pre>I've found an interesting article that explains that git bisect is
branch aware, meaning that it knows about merge commits and "does the
right thing."
<a href="http://stackoverflow.com/questions/3673377/why-isnt-git-bisect-branch-aware">http://stackoverflow.com/questions/3673377/why-isnt-git-bisect-branch-aware</a>
Thinking about the issue, I'm wondering if git's "strange" jumps back
in time for a bisect are actually _because_ of this methodology.
Perhaps I should continue with this bisect log after all? I have it
saved, so perhaps that's what I'll do.
Daniel, if you could confirm or deny my suspicions above before I go
through with all of that work, I would much appreciate it!</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>