From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Maximilian Weigand <mweigand@mweigand.net>
Cc: tools@linux.kernel.org
Subject: Re: b4: workflow for selecting to/cc targets of individual patches
Date: Fri, 2 Jun 2023 12:44:16 -0400 [thread overview]
Message-ID: <20230602-underarm-stuffy-e6e9fa@meerkat> (raw)
In-Reply-To: <bdefe087-28a2-d541-933c-ccd743cc8b62@mweigand.net>
On Wed, May 31, 2023 at 08:57:58PM +0200, Maximilian Weigand wrote:
> My understanding (also from reading a bit in the tools archive) is that
> the cover letter should be addressed to all maintainers and mailing
> lists targeted in any of the patches, while individual patches should go
> only to the maintainers (via To:) and lists (via Cc:) they are targeted at.
My (very unscientific) polling that I held at the time when I was implementing
this suggested that pretty much all maintainers want to receive the entire
series, even if only a single patch out of 10 touches their subsystem. Seeing
the whole series allows them to better understand the patch in the context of
the larger change.
> Using b4 prep --auto-to-cc is not an option here, as all To:/CC:
> addresses in the cover letter will be used in all patches (my
> understanding, based on b4 send --dry-run tests).
I believe that you should just use this option and blame the tool if someone
complains (and I highly doubt that anyone will). :)
-K
prev parent reply other threads:[~2023-06-02 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 18:57 b4: workflow for selecting to/cc targets of individual patches Maximilian Weigand
2023-05-31 20:41 ` Nathan Chancellor
2023-06-02 8:28 ` Maximilian Weigand
2023-06-02 16:44 ` Konstantin Ryabitsev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230602-underarm-stuffy-e6e9fa@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=mweigand@mweigand.net \
--cc=tools@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).