On Sat, 5 Sep 2015 23:29:05 +0000 Albert Freeman <albertwdfree...@gmail.com> wrote:
> The reply from Eric Anholt made two suggestions that should not be > difficult to implement for someone who made the patch in the first > place. Why would code be committed when improvements could be easily > made? From what I have seen, this kind of thing happens even to > experienced mesa developers who know exactly what they are doing. > > It is much better to arrive at a solution without the issue now than > wait a few years (or some other period of time) for it to be replaced > by someone who has likely forgotten the details involved with its > implementation (or by someone who did not write the code in the first > place). Oh, absolutely - I had no issues with "this needs changing". My issue was with the fact it took months to get that. Had I come up with a new patch, it would likely have taken a similar time, months again, which did not inspire confidence. Benjamin, if you want to take it forward, please do. - Lauri _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
