From: Ben Aveling <bena.001@optusnet.com.au>
To: Junio C Hamano <gitster@pobox.com>
Cc: Antoine Pelisse <apelisse@gmail.com>, Jeff King <peff@peff.net>,
"Matt Seitz (matseitz)" <matseitz@cisco.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Hilco Wijbenga <hilco.wijbenga@gmail.com>
Subject: Re: git send-email should not allow 'y' for in-reply-to
Date: Sat, 12 Jan 2013 12:02:59 +1100 [thread overview]
Message-ID: <50F0B643.20201@optusnet.com.au> (raw)
In-Reply-To: <7vmwwf9sx9.fsf@alter.siamese.dyndns.org>
On 12/01/2013 10:54 AM, Junio C Hamano wrote:
> Antoine Pelisse <apelisse@gmail.com> writes:
>
>> 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.
> Sounds sensible (even though technically you reply to a message
> that has that message ID, and not to a message ID ;-)).
>
> Any better phrasing from others? If not, I'd say we adopt this
> text.
I guess it depends on how much we mind if people accidentally miss the
message ID.
If we don't mind much, we could say something like:
What Message-ID are you replying to [Default=None]?
If we are concerned that when a Message-ID exists, it should be
provided, we could split to 2 questions:
Are you replying to an existing Message [Y/n]?
And then, if the answer is Y,
What Message-ID are you replying to?
Regards, Ben
next prev parent reply other threads:[~2013-01-12 1:12 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
2013-01-11 23:54 ` Junio C Hamano
2013-01-12 1:02 ` Ben Aveling [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50F0B643.20201@optusnet.com.au \
--to=bena.001@optusnet.com.au \
--cc=apelisse@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hilco.wijbenga@gmail.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.
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.