From: Junio C Hamano <gitster@pobox.com>
To: NeilBrown <neilb@ownmail.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] send-email: don't duplicate Reply-to: in intro message
Date: Wed, 17 Sep 2025 07:05:10 -0700 [thread overview]
Message-ID: <xmqqfrcli38p.fsf@gitster.g> (raw)
In-Reply-To: <175809074627.1696783.67425889158412786@noble.neil.brown.name> (NeilBrown's message of "Wed, 17 Sep 2025 16:32:26 +1000")
NeilBrown <neilb@ownmail.net> writes:
> Add parsing to the loop in pre_process_file() to recognise a Reply-to
> header and to store the result in $reply_to. This means that the
> intro message will not get a second header and also means that
> any changes made to the Reply-To header during editing will be
> incorporated in the $reply_to variable and so included in all the
> generated email messages.
>
> Signed-off-by: NeilBrown <neil@brown.name>
> ---
> git-send-email.perl | 3 +++
> 1 file changed, 3 insertions(+)
Makes sense.
Just FYI for any future contributions, it is customary to mark the
second iteration as [PATCH v2] on the subject and to make the
message a direct reply (with "Reply-To") to the previous iteration,
to help people find how the patch evolved in the list archives like
https://lore.kernel.org/git/
Obviously no need to redo this patch only for that, but if you need
some other changes, sending v3 as a reply to the message I am
responding to would be a good thing to do.
Thanks.
>
> diff --git a/git-send-email.perl b/git-send-email.perl
> index 437f8ac46a85..e2248c223119 100755
> --- a/git-send-email.perl
> +++ b/git-send-email.perl
> @@ -1931,6 +1931,9 @@ sub pre_process_file {
> $in_reply_to = $1;
> }
> }
> + elsif (/^Reply-To: (.*)/i) {
> + $reply_to = $1;
> + }
> elsif (/^References: (.*)/i) {
> if (!$initial_in_reply_to || $thread) {
> $references = $1;
prev parent reply other threads:[~2025-09-17 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 6:32 [PATCH] send-email: don't duplicate Reply-to: in intro message NeilBrown
2025-09-17 6:56 ` Eric Sunshine
2025-09-17 14:05 ` Junio C Hamano [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=xmqqfrcli38p.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=neilb@ownmail.net \
/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).