<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c18">Comment # 18</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 <span class="vcard"><a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> <span class="fn">Ilia Mirkin</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=81500#c16">comment #16</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=81500#c15">comment #15</a>)
> > Unlikely. Stable releases tend to contain cherry-picks of patches from
> > master, not patches attached to random bugs. (Exceptions can of course be
> > made.)
>
> for me with my ati radeon HD4650 ( who uses r600 driver ) it's not a random
> bug, the bug is always reproducible with flightgear 3.0.0,</span >
I meant "bugzilla bugs". This is just not how development is done in mesa (or
most open-source projects).
<span class="quote">> > Perhaps it got reverted/somehow fixed? If you can figure out what fixes this
> > in master, it can be cherry-picked back to the 10.2 branch for the next
> > stable release. Or if the fixes are deemed too invasive, perhaps the revert
> > will indeed be appropriate.
>
> I think also that someone who works in 10.2 branch has reverted this commit
> because he found some bugs or strange results in test softwares like piglit ?</span >
Not sure what you're saying... no one "works in 10.2 branch". Development is
done on master, and fixes get cherry-picked back to the stable branches. Of
course sometimes fixes are made "accidentally", or someone forgets that the fix
would apply to a previous release, or whatever.
In this case, sounds like the fix is already in master. So it's a question of
identifying which commit it is, and cherry-picking it back to the 10.2 branch,
or figuring out a different approach if the fix is deemed too invasive.</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>