git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Raymond E. Pasco" <ray@ameretat.dev>
To: "Junio C Hamano" <gitster@pobox.com>, "Drew DeVault" <sir@cmpwn.com>
Cc: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] send-email: do not prompt for In-Reply-To
Date: Thu, 27 Aug 2020 21:44:11 -0400	[thread overview]
Message-ID: <C588ZA2QAFBS.23DYVMBK3E0X6@ziyou.local> (raw)
In-Reply-To: <xmqqsgc7oa5s.fsf@gitster.c.googlers.com>

On Thu Aug 27, 2020 at 9:02 PM EDT, Junio C Hamano wrote:
> I agree that it is likely that only very small population even gets
> bittn by this "in-reply-to gets prompted" issue, because it is
> unlikely for users not to give "to:" address in one way or another
> and let the prompt logic to ask them.

The merits of this thread's proposal aside, send-email's prompting has
always seemed half-baked to me - it often doesn't even show up, and
doesn't prompt for some things that would be useful like additional CCs
(and if you're setting In-Reply-To, there are probably additional CCs).

The prompts have helped me not flub emails before, but arguably that's
not good since they're often not even shown and someone may come to rely
on their presence only to later accidentally turn them off.

Anyway, it's worth noting that, because the prompts *do* exist,
half-baked as they are, it's not really safe to assume that nobody sees
them. There might be a sizable population out there never specifying
"--to" because they know they'll be prompted for it.

  parent reply	other threads:[~2020-08-28  1:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 17:55 [PATCH] send-email: do not prompt for In-Reply-To Drew DeVault
2020-08-27 19:04 ` Junio C Hamano
2020-08-27 19:08   ` Junio C Hamano
2020-08-27 19:14     ` Drew DeVault
2020-08-27 19:20       ` Carlo Marcelo Arenas Belón
2020-08-27 19:23         ` Drew DeVault
2020-08-27 19:32           ` Carlo Marcelo Arenas Belón
2020-08-27 19:34         ` Junio C Hamano
2020-08-27 19:34           ` Drew DeVault
2020-08-27 19:46             ` Carlo Arenas
2020-08-27 22:02           ` Carlo Marcelo Arenas Belón
2020-08-27 22:57             ` Junio C Hamano
2020-08-27 22:59               ` Drew DeVault
2020-08-27 23:05                 ` Drew DeVault
2020-08-28  1:02                   ` Junio C Hamano
2020-08-28  1:10                     ` Drew DeVault
2020-08-28  1:44                     ` Raymond E. Pasco [this message]
2020-08-28  1:56                       ` Drew DeVault
2020-08-27 23:23                 ` Junio C Hamano
2020-08-27 23:24                   ` Drew DeVault
2020-08-28 18:39               ` Drew DeVault
2020-08-28 20:58                 ` Raymond E. Pasco
2020-08-28 21:00                 ` Junio C Hamano
2020-08-28 21:01                   ` Drew DeVault
2020-08-28 21:33                     ` Junio C Hamano
2020-08-28 21:35                       ` Drew DeVault
2020-08-27 19:21       ` Junio C Hamano
2020-08-27 19:22         ` Drew DeVault
2020-08-27 19:15   ` Drew DeVault

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=C588ZA2QAFBS.23DYVMBK3E0X6@ziyou.local \
    --to=ray@ameretat.dev \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).