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

Re: [PATCH] send-email: validate & reconfirm interactive responses

From
Stephen Boyd <bebarino@gmail.com>
Date
Sep 6, 2012, 21:47 UTC
Message-ID
<CALaEz9ULAAoX0P-Tp7Ma0UmWqRvenkG3OEQPQyE6iqwdV6Kxig@mail.gmail.com>
In-Reply-To
<7vipbq3omb.fsf@alter.siamese.dyndns.org>
On Thu, Sep 6, 2012 at 1:03 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
>
> If you let $to to go empty with the first hunk of your patch, where
> does the mail eventually go?  Does anybody later in the code decide
> to add some recipient?  If there is a reason why an empty input is a
> valid here, I think there is a stronger need (that is, stronger than
> the above ase for $initial_reply_to) to explain when the user wants
> to leave this empty.
>

I almost never type anything and just use the To header in the patch I want to send.

Previous: Stephen Boyd
Message 13 of 13 in “send-email and in-reply-to = n”
  1. Stephen BoydAug 13, 2012
  2. Junio C HamanoAug 13, 2012
  3. Martin von ZweigbergkAug 14, 2012
  4. send-email: validate & reconfirm interactive responsesJunio C Hamano, Aug 14, 2012
  5. Martin von ZweigbergkAug 14, 2012
  6. Junio C HamanoAug 14, 2012
  7. Stephen BoydSep 5, 2012
  8. Junio C HamanoSep 6, 2012
  9. Stephen BoydSep 6, 2012
  10. Junio C HamanoSep 6, 2012
  11. send-email: initial_to and initial_reply_to are both optionalJunio C Hamano, Sep 6, 2012
  12. Stephen BoydSep 6, 2012
  13. Stephen BoydSep 6, 2012

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.