git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Antoine Pelisse <apelisse@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
	"Matt Seitz (matseitz)" <matseitz@cisco.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git send-email should not allow 'y' for in-reply-to
Date: Fri, 11 Jan 2013 23:42:28 +0100	[thread overview]
Message-ID: <CALWbr2wtAzz7yWb_Z_V0LFt5ddZcRSs7_rea2w=ghdC847mEyQ@mail.gmail.com> (raw)
In-Reply-To: <7vy5fz9xdl.fsf@alter.siamese.dyndns.org>

On Fri, Jan 11, 2013 at 11:18 PM, Junio C Hamano <gitster@pobox.com> wrote:
> The exchange, when you do not have a configuration, goes like this:
>
>     $ git send-email 0001-filename-of-the-patch.patch
>     0001-filename-of-the-patch.patch
>     Who should the emails be sent to (if any)? junio
>     Are you sure you want to use <junio> [y/N]? y
>     Message-ID to be used as In-Reply-To for the first email (if any)?
>
> Why not do this instead?
>
>     $ git send-email 0001-filename-of-the-patch.patch
>     0001-filename-of-the-patch.patch
>     Who should the emails be sent to (if any)? junio
>     Are you sure you want to use <junio> [y/N]? y
>     Is this a response to an existing message [y/N]? y

I'm not sure about the extra question. If the user doesn't care, he
will probably use the empty default, which will result in the same
number of steps. If the user cares, he probably knows what he's doing
and will give a sensible value.

>     What is the Message-ID of the message you are replying to?

I would simply go for:

  What Message-ID are you replying to (if any)?

If I don't know what to answer, I would definitely not say y/yes/n/no,
but press enter directly.

  reply	other threads:[~2013-01-11 22:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 20:13 git send-email should not allow 'y' for in-reply-to Matt Seitz (matseitz)
2013-01-11 21:23 ` Jeff King
2013-01-11 21:53   ` Antoine Pelisse
2013-01-11 22:18     ` Junio C Hamano
2013-01-11 22:42       ` Antoine Pelisse [this message]
2013-01-11 23:54         ` Junio C Hamano
2013-01-12  1:02           ` Ben Aveling
2013-01-12  2:56             ` Junio C Hamano
     [not found] <1357885869-20815-1-git-send-email-cyliu@suse.com>
     [not found] ` <50EFD066.60501@redhat.com>
2013-01-11 16:39   ` Eric Blake
2013-01-11 16:47     ` Jeff King
2013-01-11 17:51       ` Eric Blake
2013-01-11 18:43       ` Hilco Wijbenga
2013-01-11 18:54         ` Jeff King
2013-02-24  9:03           ` Junio C Hamano

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='CALWbr2wtAzz7yWb_Z_V0LFt5ddZcRSs7_rea2w=ghdC847mEyQ@mail.gmail.com' \
    --to=apelisse@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=matseitz@cisco.com \
    --cc=peff@peff.net \
    /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).