On Thu, May 25, 2017 at 7:37 AM, Lukas Wunner <lukas@xxxxxxxxx> wrote: > On Wed, May 24, 2017 at 11:28:12AM +0200, Daniel Vetter wrote: >> We can't check this when applying (since r-b/a-b tags often get added >> afterwards), but we can check this when pushing. This only looks at >> patches authored by the pusher. > > BTW, can we also have a rule that large drivers (i.e. with a large user > base) are required to provide at least one person at all times (or at > least outside the merge window) who is able to review fixes, push them > to the driver's repo and send a timely pull to Dave? > > On multiple occasions I've seen Dave send a fixes pull with an apology > along the lines of "a bit more than usual at this time of the cycle > because it includes two weeks worth of driver XYZ fixes". AMD is already planning to swtich to a group/committer model, I just discussed that with Alex. That takes care of the huge drivers (intel/amd) and the small ones (if they are in drm-misc). No idea what we'll end up doing with the medium sized drivers, but I guess that's a discussion for the next months/years ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
