<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - wrong color in flightgear for the c172p if "Atmospheric light scattering" is used" href="https://bugs.freedesktop.org/show_bug.cgi?id=81500#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - wrong color in flightgear for the c172p if "Atmospheric light scattering" is used" href="https://bugs.freedesktop.org/show_bug.cgi?id=81500">bug 81500</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="show_bug.cgi?id=81500#c19">comment #19</a>) > (In reply to <a href="show_bug.cgi?id=81500#c14">comment #14</a>) > > and I notice that mesa 10.3.x doesn't have the bug ( because the file > > /src/glsl/link_varyings.cpp doesn't have the changes made by the faulty > > commit d030a3404ca0fedf365cb0fd41eaad7abc8ff132 ) > > I made a mistake here, in fact the file /src/glsl/link_varyings.cpp in 10.3 > branch has the changes made by the commit > d030a3404ca0fedf365cb0fd41eaad7abc8ff132, > > but the difference is that some commits in 10.3 branchs has solved the bug, > because the 10.3 version of /src/glsl/link_varyings.cpp is not identical to > the 10.2.4 version, > > by retracing the changes between 10.2.4 and 10.3.x for this file I think I > can identify the commit who has solved the bug Just a word of caution -- the fix might have been to a different part of the code, and not to that particular file. You can use bisect again to figure out the change that fixed it, just reverse the meanings of 'good' and 'bad'. A "good" commit would be one that has the issue, and a "bad" commit would be one where the issue is resolved. Then the first "bad" commit will point you at the commit that resolves the problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>