On Mon, 15 Feb 2021 17:43:59 +0000, Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote: > For bigger patchsets, you should combine get_maintainer.pl with sending > emails so individual patches will go to all role-based entries from > get_maintainer.pl and to all mailing lists. You can (and sometimes even > worth to) skip proposals based on git-history. > > Then the cover letter which should go to everyone... or most of people > and linked from individual patches. > > For example the easiest I think: > 1. Put all folks and lists as "Cc:" in cover letter. > 2. Send everything: > git send-email --cc-cmd "scripts/get_maintainer.pl --no-git --no-roles --no-rolestats" --to linux-kernel@xxxxxxxxxxxxxxx 0* > > Optionally you could add --no-git-fallback to get_maintainer if it > proposes some irrelevant addresses. > > Other way is to send first cover letter and then reference it via > in-reply-to: > > 1. To get everyone for cover letter: > scripts/get_maintainer.pl --no-multiline --interactive --separator=\'' --to '\' --no-git --no-roles --no-rolestats 00* > > 2. git send-email --cc linux-kernel@xxxxxxxxxxxxxxx ... 0000* > > 3. Finally all patches with in-reply-to: > git send-email --cc-cmd "scripts/get_maintainer.pl --no-git --no-roles --no-rolestats" --to linux-kernel@xxxxxxxxxxxxxxx --no-thread --in-reply-to='foo-bar-xxxxxxx' 000[123456789]-* 00[123456789]*-* I personally dislike this method as a recipient. Context matters, and seeing how an isolated patch fits in a bigger series is pretty important. I can mark the patches I don't care about quicker than you can say "Don't care", and it saves me having to drag the mbox via lore and import it. That's only me, but I suspect I'm not the only one with that particular flow. Thanks, M. -- Without deviation from the norm, progress is not possible.
