From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org, ps@pks.im, sunshine@sunshineco.com,
"Sören Krecker" <soekkle@freenet.de>
Subject: Re: [PATCH v3 1/4] add-patch: Fix type conversion warnings from msvc
Date: Thu, 30 Jan 2025 11:24:20 -0800 [thread overview]
Message-ID: <xmqqbjvocdgb.fsf@gitster.g> (raw)
In-Reply-To: <57031bce-6dc4-48a7-b4b5-1b837ea3ab8f@gmail.com> (Phillip Wood's message of "Thu, 30 Jan 2025 10:47:22 +0000")
Phillip Wood <phillip.wood123@gmail.com> writes:
> On 29/01/2025 19:52, Junio C Hamano wrote:
>> Phillip Wood <phillip.wood123@gmail.com> writes:
>> By the way, who is
>> <CAPig+cQ49Hdc_8=mRhhJDTny_Kqo6Wg6Nr98rsBN_YXmBrQ6kA@mail.gmail.com>
>> and why is such an apparently bogus e-mail address Cc'ed?
>
> That's the Reply-To address from the mail I was replying
> to. Unfortunately it does not seem to exist.
It just occured to me that it is probably added by a mistake and the
sender really wanted to add it to In-Reply-To: instead of Reply-To:
I wonder if this is a mistake we can do something to help users
avoid? "git send-email" has the "--reply-to=" option and there is a
valid use case for that option, so disabling that option is a
non-starter.
Of course there are other ways to send e-mailed patches, but I do
not think of a way to misuse them with reply-to and in-reply-to
mixed up.
Thoughts?
next prev parent reply other threads:[~2025-01-30 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 12:56 [PATCH v3 0/4] Fix type conversion Warings from msvc Sören Krecker
2025-01-26 12:56 ` [PATCH v3 1/4] add-patch: Fix type conversion warnings " Sören Krecker
2025-01-27 7:26 ` Patrick Steinhardt
2025-01-27 16:10 ` Junio C Hamano
2025-01-29 16:51 ` Phillip Wood
2025-01-29 19:52 ` Junio C Hamano
2025-01-30 10:47 ` Phillip Wood
2025-01-30 19:24 ` Junio C Hamano [this message]
2025-01-27 7:26 ` [PATCH v3 0/4] Fix type conversion Warings " Patrick Steinhardt
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=xmqqbjvocdgb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
--cc=ps@pks.im \
--cc=soekkle@freenet.de \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.