<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - [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#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - [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:damien.lespiau@gmail.com" title="Damien Lespiau <damien.lespiau@gmail.com>"> <span class="fn">Damien Lespiau</span></a>
</span></b>
<pre>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.</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>