git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git send-email should not allow 'y' for in-reply-to

From
BABen Aveling <bena.001@optusnet.com.au>
Date
Jan 12, 2013, 01:02 UTC
Message-ID
<50F0B643.20201@optusnet.com.au>
In-Reply-To
<7vmwwf9sx9.fsf@alter.siamese.dyndns.org>
On 12/01/2013 10:54 AM, Junio C Hamano wrote:
Show 13 quoted lines
> 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
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 8 in “Re: git send-email should not allow 'y' for in-reply-to”
  1. Matt Seitz (matseitz)Jan 11, 2013
  2. Jeff KingJan 11, 2013
  3. Antoine PelisseJan 11, 2013
  4. Junio C HamanoJan 11, 2013
  5. Antoine PelisseJan 11, 2013
  6. Junio C HamanoJan 11, 2013
  7. Ben AvelingJan 12, 2013
  8. Junio C HamanoJan 12, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.