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

Re: [RFC] send-email quote issues

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jun 15, 2015, 11:32 UTC
Message-ID
<vpqmw011a22.fsf@anie.imag.fr>
In-Reply-To
<330077615.505681.1434367014434.JavaMail.zimbra@ensimag.grenoble-inp.fr>
Remi Lespinet <remi.lespinet@ensimag.grenoble-inp.fr> writes:
> Currently, git send-email contains a function which splits at commas
> with respect to quotes (parse_address_line introduced by
> 5012699d9840fe34fe0838ea0d529c2f32f76b82).

It seems I had missed this one, but indeed, it should probably be used instead of split_at_commas in your series.

Show 5 quoted lines
> It is used to parse user input when there's no recipient specified. I
> would like to use this function to parse --to, --cc and --bcc options,
> but the execution of this function depends on whether the user has the
> Perl library Mail::Address or not. This introduce a change in the
> behaviour:

I would say that using parse_address_line is good for consistancy in Git anyway. If the behavior of parse_address_line is broken on some corner-cases, then it should be fixed anyway.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Remi LespinetNext: Remi Lespinet
Message 2 of 5 in “[RFC] send-email quote issues”
  1. Remi LespinetJun 15, 2015
  2. Matthieu MoyJun 15, 2015
  3. Remi LespinetJun 15, 2015
  4. Matthieu MoyJun 15, 2015
  5. Remi LespinetJun 15, 2015

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.