On Tue, May 8, 2018 at 2:20 PM, Dylan Baker <dy...@pnwbakers.com> wrote:
> Quoting Mark Janes (2018-05-08 11:10:19) > > Dylan Baker <dy...@pnwbakers.com> writes: > > > > > I have both pulled into the 18.1-proposed tree now. I think we need to > have a > > > wider discussion about better ways to propose patches to stable after > the fact > > > like ea1fff4416036066cff51826f95b4703d7211008. Thanks for helping get > this > > > resolved so quickly. > > > > We have to expect that stable annotations will be missed for some > > patches. No one is perfect. The patch author could help a lot by > > making sure the commit gets into the correct stable branches, because > > they are the ones with the most awareness of the situation. > > > > I agree 100%. > > I'm just trying to think of a more robust solution than manually mailing > mesa-stable. The signal to noise ratio of that list is pretty bad. I'm > wondering if after the fdo migration to gitlab it would be better to use > pull > requests for these kind of nominations. > A pull request is something I'm probably going to use for missed patches. AMD has its own stable branches mirroring Mesa stable branches for our official driver releases, and we have some fixes there that were not applied to upstream stable branches for various reasons. So we can easily see the diff between upstream and internal. Marek
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
