From: Jeff King <peff@peff.net>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git send-email: incorrectly parses email address with comma
Date: Sat, 12 May 2018 05:48:50 -0400 [thread overview]
Message-ID: <20180512094849.GI28279@sigill.intra.peff.net> (raw)
In-Reply-To: <9a35041b-8333-9533-4344-08d6ef99c9c9@gmx.de>
On Sat, May 12, 2018 at 10:21:46AM +0200, Heinrich Schuchardt wrote:
> Git send-email allows to combine multiple email addresses in one
> parameter, e.g.
>
> --to="a@example.com, b@example.com"
>
> But email addresses may contain commas themselves:
>
> --to="LASTNAME, firstname <firstname.lastname@example.com>"
>
> This may lead to an error:
If the name contains syntactically relevant metacharacters, it can be
quoted. So as a workaround, you can do:
--to='"LASTNAME, firstname" <firstname.lastname@example.com>'
I think rfc822 actually requires even names with just spaces in them to
be quoted, but git-send-email and most other mail programs are pretty
lax about allowing just about anything outside of the <>, so people tend
not to bother.
> If the string preceding a comma is not a valid email address do not
> split it off.
That might work as a heuristic, though "is a valid email address" is a
notoriously hard thing to check. Possibly looking for an "@" would catch
most common cases, though.
-Peff
next prev parent reply other threads:[~2018-05-12 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 8:21 [BUG] git send-email: incorrectly parses email address with comma Heinrich Schuchardt
2018-05-12 9:48 ` Jeff King [this message]
2018-05-12 21:07 ` Heinrich Schuchardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180512094849.GI28279@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=xypron.glpk@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).