From: Junio C Hamano <gitster@pobox.com>
To: Remi LESPINET <remi.lespinet@ensimag.grenoble-inp.fr>
Cc: git@vger.kernel.org,
Remi Galan <remi.galan-alfonso@ensimag.grenoble-inp.fr>,
Guillaume Pages <guillaume.pages@ensimag.grenoble-inp.fr>,
Louis-Alexandre Stuber
<louis--alexandre.stuber@ensimag.grenoble-inp.fr>,
Antoine Delaite <antoine.delaite@ensimag.grenoble-inp.fr>,
Jorge Juan Garcia Garcia
<Jorge-Juan.Garcia-Garcia@ensimag.imag.fr>,
Mathieu Lienard--Mayor <Mathieu.Lienard--Mayor@ensimag.imag.fr>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH/RFC] send-email: allow multiple emails using --cc --to and --bcc
Date: Fri, 29 May 2015 09:13:06 -0700 [thread overview]
Message-ID: <xmqqa8wne50t.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87oal32wuj.fsf@ensimag.grenoble-inp.fr> (Remi LESPINET's message of "Fri, 29 May 2015 18:05:08 +0200")
Remi LESPINET <remi.lespinet@ensimag.grenoble-inp.fr> writes:
> Yes, that works if Foo is in an alias file, so that's clearly a bad
> example, I added quotes:
>
> git send-email --to='"Foo, Bar" <foobar@example.com>'
I'd further suggest replacing ", Bar" with something a bit more
realistic that people use in real life, e.g. ", Esq." or ", PhD"
(e.g. "Jane Doe, Esq.")
next prev parent reply other threads:[~2015-05-29 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 10:42 [PATCH/RFC] send-email: allow multiple emails using --cc --to and --bcc Remi Lespinet
2015-05-28 10:42 ` Remi Lespinet
2015-05-28 11:47 ` Matthieu Moy
2015-05-28 15:26 ` Eric Sunshine
2015-05-28 18:02 ` Eric Sunshine
2015-05-29 16:07 ` Remi LESPINET
2015-05-28 17:45 ` Junio C Hamano
2015-05-29 16:05 ` Remi LESPINET
2015-05-29 16:13 ` Junio C Hamano [this message]
2015-05-29 17:55 ` Matthieu Moy
2015-05-29 18:04 ` Junio C Hamano
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=xmqqa8wne50t.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Jorge-Juan.Garcia-Garcia@ensimag.imag.fr \
--cc=Mathieu.Lienard--Mayor@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=antoine.delaite@ensimag.grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=guillaume.pages@ensimag.grenoble-inp.fr \
--cc=louis--alexandre.stuber@ensimag.grenoble-inp.fr \
--cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
--cc=remi.lespinet@ensimag.grenoble-inp.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.