<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> <span class="fn">Imre Deak</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [HSW-M Bisected]multiple small screen shows while running testdisplay -f / fastboot=1 pfit bug"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76153">bug 76153</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>ASSIGNED
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [HSW-M Bisected]multiple small screen shows while running testdisplay -f / fastboot=1 pfit bug"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76153#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [HSW-M Bisected]multiple small screen shows while running testdisplay -f / fastboot=1 pfit bug"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76153">bug 76153</a>
from <span class="vcard"><a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> <span class="fn">Imre Deak</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=76153#c16">comment #16</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=76153#c15">comment #15</a>)
> > Hi Gordon,
> >
> > Reverting the bisected commit is the best way to make sure the bisect result
> > makes sense. git bisect often ends up in a commit that is not the culprit
> > and knowing if a git revert fixes the issues is a definitive way to be sure.
> >
> > I'd argue that should be the last step in the bisect script, give this info.
> > Sometimes a git revert is not possible or easy though, in which case we
> > can't do that.
>
> Damien, I fully agree with you that reverting the bisected commit is the
> best way to ensure the bisect result (although it doesn't always apply).
>
> But in this case, I don't think Imre is doubting the bisect result.
> Instead, the bug has been fixed, and he wants to know which commit fixes
> the bug. I'd check if this is really necessary as it won't be trivial
> effort (as the test is not automated so auto-bisect won't help here).</span >
Yes, I wanted to know which commit fixed the issue. But I realize that at this
point it's not worth the effort: the bug was reported too long time ago and
based on <a href="show_bug.cgi?id=76153#c17">comment 17</a>, the bisect result isn't useful any more (either because
the bisect result wasn't correct in the first place or something above the
kernel fixed/hid the bug). Assuming this fixed now.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>