[Mesa-dev] [Bug 81500] wrong color in flightgear for the c172p if "Atmospheric light scattering" is used
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Jul 20 09:26:26 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=81500
--- Comment #18 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to comment #16)
> (In reply to comment #15)
> > 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,
I meant "bugzilla bugs". This is just not how development is done in mesa (or
most open-source projects).
> > 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 ?
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.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140720/48f0865b/attachment-0001.html>
More information about the mesa-dev
mailing list