Hi Jani, On Thu, Sep 19, 2019 at 10:49 AM Jani Nikula <jani.nikula@xxxxxxxxx> wrote: > On Thu, 19 Sep 2019, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > > On Thu, Sep 19, 2019 at 8:57 AM Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote: > >> On Wed, Sep 18, 2019 at 10:57:28AM -0300, Mauro Carvalho Chehab wrote: > >> 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". > > > > Better: perhaps get_maintainer.pl can be taught to add the author of the > > commit pointed to by the Fixes tag, if present? > > The drm maintainer tools [1] have that, with Cc's and reviewers picked > up, and appropriate Cc: stable added. On a random commit from v5.3: Thanks, but that's not scripts/get_maintainer.pl, and restricted to one out of N subsystems. Not so dissimilar from what Dan was complaining about. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds