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

Re: git send-email --notmuch expr

From
Jed Brown <jed@59a2.org>
Date
Nov 25, 2009, 13:06 UTC
Message-ID
<87aaya69eg.fsf@59A2.org>
In-Reply-To
<m3hbsic3l5.fsf@localhost.localdomain>
On Wed, 25 Nov 2009 02:16:52 -0800 (PST), Jakub Narebski <jnareb@gmail.com> wrote:
> (?: ... ) is in Perl non-capturing grouping

Thanks. Actually that code only executes under --compose, the headers provided by format-patch all just come through untouched (but all the interesting ones are duplicated). So it looks like we just need to actually parse the relevant headers from format-patch, before the part where the user gets prompted. These are a little harder because they can span multiple lines. The current validation with --compose is a bit broken: suppose the user sets the perfectly valid header

To: foo@example.com,
    bar@example.com

The validation will strip the first line while issuing warning, but send the second through untouched.

Jed
Previous: Jakub Narebski
Message 5 of 5 in “git send-email --notmuch expr”
  1. Jed BrownNov 25, 2009
  2. 1/2 Added the --notmuch option to git format-patch.Jed Brown, Nov 25, 2009
  3. 2/2 Documentation for format-patch --notmuch.Jed Brown, Nov 25, 2009
  4. Jakub NarebskiNov 25, 2009
  5. Jed BrownNov 25, 2009

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.