From: Junio C Hamano <gitster@pobox.com>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH v4] git-send-email: Use sanitized address when reading mbox body
Date: Wed, 03 Jul 2024 08:44:30 -0700 [thread overview]
Message-ID: <xmqq5xtmfpk1.fsf@gitster.g> (raw)
In-Reply-To: <dbdaf27a-4b11-44eb-ada7-9991628a47ce@prolan.hu> ("Csókás Bence"'s message of "Wed, 3 Jul 2024 08:24:27 +0200")
Csókás Bence <csokas.bence@prolan.hu> writes:
> On 7/1/24 20:47, Junio C Hamano wrote:
>> Let's mark it for 'next' soonish, with proposed log message
>> rewritten somewhat.
>> Thanks.
>> ----- >8 -----
>
> Alright. Should I re-send it with this message then, or will you amend it?
If you are 100% happy with what you saw there, then just saying so
would be sufficient. If not, you can update your commit with
further improvements and send a v5 iteration.
Thanks.
prev parent reply other threads:[~2024-07-03 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 9:01 [PATCH v4] git-send-email: Use sanitized address when reading mbox body Csókás, Bence
2024-07-01 18:47 ` Junio C Hamano
2024-07-03 6:24 ` Csókás Bence
2024-07-03 15:44 ` 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=xmqq5xtmfpk1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=csokas.bence@prolan.hu \
--cc=git@vger.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).