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, 13:52 UTC
Message-ID
<vpqd20xxenv.fsf@anie.imag.fr>
In-Reply-To
<999870154.509851.1434373434414.JavaMail.zimbra@ensimag.grenoble-inp.fr>
Remi Lespinet <remi.lespinet@ensimag.grenoble-inp.fr> writes:
> Ok, but I don't know what fixed means in these particular cases.
> Actually the problem when we have a quote in a name is: Is this a
> delimiter or is this an ascii char?

To me, the answer should be: do whatever the RFC says in email headers. I'd expect anything that works in the To: header to work in the --to option of git send-email.

If I read correctly, this is address-list in RFC 2822.

Now, when the address list is invalid wrt the RFC, we can either reject it or try to guess.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Remi LespinetNext: Remi Lespinet
Message 4 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.