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
Antoine Pelisse <apelisse@gmail.com>
Date
Jan 11, 2013, 22:42 UTC
Message-ID
<CALWbr2wtAzz7yWb_Z_V0LFt5ddZcRSs7_rea2w=ghdC847mEyQ@mail.gmail.com>
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:
Show 15 quoted lines
> 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.

Previous: Junio C HamanoNext: Junio C Hamano
Message 5 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.