From: Junio C Hamano <gitster@pobox.com>
To: "Drew DeVault" <sir@cmpwn.com>
Cc: "Jeff King" <peff@peff.net>, <git@vger.kernel.org>
Subject: Re: [PATCH v4] format-patch: --rfc honors what --subject-prefix sets
Date: Fri, 01 Sep 2023 09:48:44 -0700 [thread overview]
Message-ID: <xmqq1qfhrg9f.fsf@gitster.g> (raw)
In-Reply-To: <CV7EK073OLB2.3Q4Y31O55ZY9P@taiga> (Drew DeVault's message of "Fri, 01 Sep 2023 09:29:00 +0200")
"Drew DeVault" <sir@cmpwn.com> writes:
> +1 to proposed changes
Thanks, let's merge that version to 'next' then.
prev parent reply other threads:[~2023-09-01 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 6:43 [PATCH v4] format-patch: --rfc honors what --subject-prefix sets Drew DeVault
2023-08-30 19:28 ` Junio C Hamano
2023-08-31 21:29 ` Jeff King
2023-08-31 22:04 ` Junio C Hamano
2023-08-31 22:32 ` Jeff King
2023-09-01 7:29 ` Drew DeVault
2023-09-01 16:48 ` 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=xmqq1qfhrg9f.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sir@cmpwn.com \
/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).