git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "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 16:23:40 -0700	[thread overview]
Message-ID: <xmqq4konptab.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <C585GT9K2V93.4O470Q21FXFD@homura> (Drew DeVault's message of "Thu, 27 Aug 2020 18:59:01 -0400")

"Drew DeVault" <sir@cmpwn.com> writes:

> On Thu Aug 27, 2020 at 6:57 PM EDT, Junio C Hamano wrote:
>> To help those who do not want to add this header, it would probably
>> be more helpful to tell what to do when prompted (like "you can give
>> an empty answer to tell the command that you are not responding to
>> any message").
>
> I don't like this solution. We should make it harder to do the wrong
> thing, and easier to do the right thing.

Carlo and I were discussing how best to describe the behaviour we
have better to the users, which is unrelated to any code change that
would be required to "make it harder make it easier."  

We need to do so to help users in the meantime, before any behaviour
change (which need to happen over several releases, as outlined
earlier) happens.





  parent reply	other threads:[~2020-08-27 23:25 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
2020-08-28  1:56                       ` Drew DeVault
2020-08-27 23:23                 ` Junio C Hamano [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq4konptab.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).