[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928807: unblock: mesa/18.3.6-2



Hi Paul,

On Thu, May 30, 2019 at 09:58:14PM +0200, Paul Gevers wrote:
> Control: tags -1 moreinfo
> 
> Hi Andreas,
> 
> On Sat, 11 May 2019 16:43:45 +0200 Andreas Boll <aboll@debian.org> wrote:
> > This unblock request contains a stable upstream release with lots of
> > bug fixes for mesa's graphics drivers including fixes for driver
> > crashes and visual corruption. It fixes two RC bugs (#922346,
> > #926857).
> 
> How would a targeted fix look like? New upstream releases don't meet the
> freeze policy and the diff is way to big to properly review.
> 
> Paul
> 

Mesa upstream is very conservative in which patches it includes into
its stable releases. Those cherry-picked patches are all targeted
fixes. No new features and also no huge fixes are allowed. See also
[1]. They also do lots of regression testing on those stable releases.

I'd be in favor of taking all fixes from the upstream stable release
and not only just those which explicitly fix reported Debian RC bugs.

I'd recommend to review the git branch patch by patch instead of the
whole diff at once. Those patches have good commit messages which help
to review the patches.

E.g.
    git clone https://salsa.debian.org/xorg-team/lib/mesa.git
    cd mesa
    gitk mesa-18.3.4-2..mesa-18.3.6-2

Does this help?

Thanks,
Andreas

[1] https://mesa3d.org/submittingpatches.html#criteria


Reply to: