[Ksummit-discuss] "Maintainer summit" invitation discussion

Michael Ellerman mpe at ellerman.id.au
Fri Apr 21 10:34:10 UTC 2017

Mauro Carvalho Chehab <mchehab at s-opensource.com> writes:

> Em Wed, 19 Apr 2017 13:20:37 -0700
> James Bottomley <James.Bottomley at HansenPartnership.com> escreveu:
>>    1. Since most people agree that these form of notifications are useful,
>>       should we have a standard email for it (or at least a list of things
>>       which should be in that email, like commit-id, tree, maintainer,
>>       mailing list and the version of the kernel it is expected to be
>>       pushed for).
>>    2. Given that we all run ad-hoc infrastructure to produce these emails,
>>       could we get a set of blessed scripts up on kernel.org for all
>>       comers so we can use the central infrastructure rather than rolling
>>       our own.
> I suspect that this very much depends on the way each maintainer handle
> patches. For subsystems like media, where we use patchwork, notification
> comes for free with the tool.

AFAIK patchwork can only notify the submitter of the patch, which is OK,
but I think it's preferable if the notification goes to the recipient
list of the original mail.

For example it's quite handy to know when another maintainer has merged
a patch, so you don't merge it too, or wonder if you should.


More information about the Ksummit-discuss mailing list