tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maximilian Weigand <mweigand@mweigand.net>
To: tools@linux.kernel.org
Subject: b4: workflow for selecting to/cc targets of individual patches
Date: Wed, 31 May 2023 20:57:58 +0200	[thread overview]
Message-ID: <bdefe087-28a2-d541-933c-ccd743cc8b62@mweigand.net> (raw)

Hi everyone,

as a very new and inexperienced patch submitter I am currently
struggling to properly prepare/submit a patch set where patches are
targeted at different maintainers and would be interested in the
proposed way to do this using b4:

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.

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).

Therefore, the only way I currently see is to populate individual
commits/patches with To:/Cc: lines in their respective trailers, e.g.
based on suitable (manual) calls to get_maintainer.pl, such is used
internally by b4 prep --auto-to-cc. Is that the recommended way?

I have not seen many patches on the mailing lists that contain To:/Cc:
lines in their trailers and am wondering that behavior would be
acceptable? If yes, would it make sense to add functionality to b4 that
would populate individual patches with To:/Cc:, similar to --auto-to-cc
does for the cover letter?

Thank you very much for any help,

best regards

Maximilian

             reply	other threads:[~2023-05-31 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 18:57 Maximilian Weigand [this message]
2023-05-31 20:41 ` b4: workflow for selecting to/cc targets of individual patches Nathan Chancellor
2023-06-02  8:28   ` Maximilian Weigand
2023-06-02 16:44 ` Konstantin Ryabitsev

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=bdefe087-28a2-d541-933c-ccd743cc8b62@mweigand.net \
    --to=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 NNTP newsgroup(s).