From: Nathan Chancellor <nathan@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@linux.kernel.org
Subject: Re: Address from trailer on individual patch is sent entire series?
Date: Fri, 6 Jan 2023 17:39:06 -0700 [thread overview]
Message-ID: <Y7i/Kn9ismmly4JY@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230107001254.g6n5szh7cnkybng2@meerkat.local>
On Fri, Jan 06, 2023 at 07:12:54PM -0500, Konstantin Ryabitsev wrote:
> On Fri, Jan 06, 2023 at 12:43:59PM -0700, Nathan Chancellor wrote:
> > Yes, I think the 'send' change sounds completely reasonable!
> >
> > I do not use 'b4 prep --auto-to-cc' since I already have my own
> > 'get_maintainer.pl' workflow so I cannot really comment on how much of a
> > change that suggestion would be. I could imagine a Suggested-by: from a
> > maintainer on one patch in a series is not uncommon, which would mean
> > their Cc: would not be added to the cover letter with your suggested
> > change, meaning they might miss the whole series. That would not be good
> > but I am not sure if that is just paranoia or a real problem.
>
> Okay, this change is in master. I'll probably backport it to 0.11.y based on
> testing feedback. Please give it a whirl.
Thank you so much for the quick turnaround! This appears to work how I
would expect it to, based on both 'b4 send -d' and 'b4 send --reflect'.
Cheers,
Nathan
prev parent reply other threads:[~2023-01-07 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 1:27 Address from trailer on individual patch is sent entire series? Nathan Chancellor
2023-01-06 16:34 ` Konstantin Ryabitsev
2023-01-06 16:54 ` Nathan Chancellor
2023-01-06 19:20 ` Konstantin Ryabitsev
2023-01-06 19:43 ` Nathan Chancellor
2023-01-07 0:12 ` Konstantin Ryabitsev
2023-01-07 0:39 ` Nathan Chancellor [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=Y7i/Kn9ismmly4JY@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=konstantin@linuxfoundation.org \
--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).