<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#c50">Comment # 50</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><span class="quote">> --- <a href="show_bug.cgi?id=53926#c49">Comment #49</a> from Daniel Vetter <<a href="mailto:daniel@ffwll.ch">daniel@ffwll.ch</a>> ---
> Are you sure that the fixed versions are really included in 3.7? Since
> the drm-intel-next tree for e.g. 3.8 is usually based on some 3.6-rc
> kernel, git bisect can let you test kernel versions based on 3.6-rc
> kernels. But the actual set of patches is only included in 3.8, not
> 3.7.</span >
Actually, I'm fairly certain it is not, :). I tried to git bisect the
two commits mentioned, and bisect noted that the former was not a
parent of the latter.
<span class="quote">> To check such a case run
>
> $ git tag --contains <commit-id>
>
> it'll list all the version tags which contain the given commit. If 3.7
> is not among them, then it's just the branch-y nature of git messing
> around with you ;-) Can you please check that and if it's just that,
> continue the bisect?</span >
Certainly, I will attempt the bisect again soon. Do you know if there
is a way to bisect with only commits that are children of the branch of
the starting commit?
--
Nate</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>