Re: [PATCH] send-email: do not prompt for In-Reply-To

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 27, 2020, 19:08 UTC
Message-ID: <xmqq3647rjnt.fsf@gitster.c.googlers.com>
In-Reply-To: <xmqq7dtjrjut.fsf@gitster.c.googlers.com>

Junio C Hamano <gitster@pobox.com> writes:

Show 13 quoted lines

> Drew DeVault <sir@cmpwn.com> writes:
>
>> Most mailing lists prefer that new patchsets and their revisions are
>> placed into a new thread. Additionally, knowledge of what In-Reply-To
>> means and where to find the Message-Id to fill in are domain-specific
>> and confusing to new users. In the niche situations where this is called
>> for, the --in-reply-to flag is sufficient.
>>
>> A config option, sendemail.promptInReplyTo, has been added to re-enable
>> the old behavior.
>
> We do not break existing users' habits without a good reason, and a
> subjective "this is the way I prefer" is *not* a good reason.

Having said that (and I am not retracting anything I said in the message I am responding to), I haven't seen this prompt triggering for me when I use send-email, with or without --in-reply-to option on the command line.

Admittedly I use a wrapper around "git send-email" to add minimum set of command line options that are always used (they are --from, --envelope-sender, and --smtp-server) but I do not think they have effect on the use of in-reply-to prompt.

What are we doing differently, I wonder?