<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [AMD tahiti XT] displayport broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=107784#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [AMD tahiti XT] displayport broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=107784">bug 107784</a> from <a class="email" href="mailto:felix.schwarz@oss.schwarz.eu" title="Felix Schwarz <felix.schwarz@oss.schwarz.eu>"> Felix Schwarz</a> <pre>In reply to Sylvain BERTRAND from <a href="show_bug.cgi?id=107784#c6">comment #6</a>) > I tested several times that: > - this commit is failing. > - the commit right before this one was working. > > Then, I can reasonably say, this commit, whatever its type, is the one > breaking displayport programming. A merge commit has two parents so you need to test both. It is possible that a merge commit did indeed introduce the bug but *highly* unlikely. (apologies if you knew all of this) Sylvain: Are you familiar with "git bisect"? "git bisect" automatically take care of merge commits. Also it minimizes the number of tests you need to do.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>