On Fri, Jun 3, 2016 at 12:17 PM, ⚛ <[email protected]> wrote: > On Fri, Jun 3, 2016 at 5:54 PM, Ilia Mirkin <[email protected]> wrote: >> On Fri, Jun 3, 2016 at 11:49 AM, ⚛ <[email protected]> wrote: >>> On Fri, Jun 3, 2016 at 2:08 PM, Nicolai Hähnle <[email protected]> wrote: >>>> On 03.06.2016 13:12, wrote: >>>>> >>>>> Situation: Looking at the content displayed by the web browser for URL >>>>> http://patchwork.freedesktop.org/project/mesa/series and sub-pages >>>>> accessible via the links. >>>> >>>> >>>> Patchwork isn't really central to most people's workflow as far as I >>>> understand it. >>> >>> Ok. But how does a developer know (better: gets notified) when a patch >>> has been accepted and added to mainline mesa-git? Viewing all git log >>> messages every day because - just in case - the patch _might_ have >>> been added to mesa-git seems quite inefficient to me. >> >> The person applying the patch will send an email saying "Thanks, >> applied", or "Thanks, pushed". > > Shouldn't repetitive tasks be left to machines whenever possible?
Regular contributors have direct push access, this happens maybe once a week to once a month. Doesn't seem worth the effort of automating. -ilia _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
