On Wed, Sep 18, 2019 at 10:57:28AM -0300, Mauro Carvalho Chehab wrote: > > > +Patches for the media subsystem should be sent to the media mailing list > > > +at linux-media@xxxxxxxxxxxxxxx as plain text only e-mail. Emails with > > > +HTML will be automatically rejected by the mail server. There's no need > > > +to copy the maintainer or sub-maintainer(s). > > > > There's too much traffic on mailing lists for me to follow everything, I > > much prefer being CC'ed on patches. > > Well, by using patchwork, the best is to take a look on it at least for > the patches that you're interested. You could script something using > pwclient in order to make it easier. > > Anyway, not sure if the other sub-maintainers see the same way. From my side, > I prefer not to be c/c, as this is just more noise, as I just rely on > patchwork for media patches. What about changing this to: > > Patches for the media subsystem should be sent to the media mailing list > at linux-media@xxxxxxxxxxxxxxx as plain text only e-mail. Emails with > HTML will be automatically rejected by the mail server. It could be wise > to also copy the sub-maintainer(s). The documentation should say "Use get_maintainer.pl" and do what it says. Everything else is too complicated. Occasionally staging maintainers will complain that they aren't CC'd even though the staging/driver/README says to CC them and I am tell them "No, the responsibility is for you to add yourself to MAINTAINERS. It doesn't matter what the documentation says, you messed up so you need to stop getting annoyed with newbies for not reading the documentation when it's your fault you weren't CC'd." When I sent a patch, I use get_maintainer.pl then I add whoever the wrote the commit from the Fixes tag. Then I remove Colin King and Kees Cook from the CC list because they worked all over the tree and I know them. I also normally remove LKML if there is another mailing list but at least one subsystem uses LKML for patchwork so this isn't safe. So the safest instructions are "Use get_matainer.pl and add the person who wrote the commit in the Fixes tag". regards, dan carpenter
