<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [vdpau] Error when calling vdp_output_surface_create"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98170#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [vdpau] Error when calling vdp_output_surface_create"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98170">bug 98170</a>
from <span class="vcard"><a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> <span class="fn">Christian König</span></a>
</span></b>
<pre>Bisecting means you try to figure out what patch introduced this bug.
E.g. you know that 11.2.2 work and 12.0.1 is broken. So you checkout the source
code from git and issue "git bisect start mesa-12.0.1 mesa-11.2.2".
Now git has the list of changes between 11.2.2 and 12.0.1, so it jumps into the
middle of that list of changes.
You then compile mesa and see if this version still works.
If it works you say "git bisect good" and git will jump another quarter to the
end of the list, if it doesn't work you say "git bisect bad" and git will jump
a quarter to the beginning of the list.
This repeats until you figured out which commit caused the problem.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>