From: Junio C Hamano <gitster@pobox.com>
To: Jorge-Juan.Garcia-Garcia@ensimag.imag.fr
Cc: git@vger.kernel.org,
Mathieu Lienard--Mayor <Mathieu.Lienard--Mayor@ensimag.imag.fr>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH] send-email: allow use of basic email list in --cc --to and --bcc
Date: Tue, 18 Jun 2013 08:01:14 -0700 [thread overview]
Message-ID: <7vip1b8nut.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1371549079-19291-1-git-send-email-Jorge-Juan.Garcia-Garcia@ensimag.imag.fr> (Jorge-Juan Garcia-Garcia's message of "Tue, 18 Jun 2013 11:51:19 +0200")
Jorge-Juan.Garcia-Garcia@ensimag.imag.fr writes:
> From: Jorge Juan Garcia Garcia <Jorge-Juan.Garcia-Garcia@ensimag.imag.fr>
>
> Make it so that we can use a list of email in flags
> instead of having to use one flag per email address.
>
> The format of email list handled is pretty basic for now:
> $ git send-email --to='Foo <foo@example.com>, bar@example.com'
> We thought it would be nice to have a "first-step" version which works
> before handling more complex ones such as:
> $ git send-email --to='Foo, Bar <foobar@example.com>'
Doesn't
git send-email --to='Foo <foo@example.com>' --to='bar@example.com'
work? If it does, I do not see much point of this change. If you
are starting from two pieces of information, why combine it into
one, only have the program to split it again, risking to be bitten
by bugs, and changing the code to do so, risking to add new bugs?
next prev parent reply other threads:[~2013-06-18 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 9:51 [PATCH] send-email: allow use of basic email list in --cc --to and --bcc Jorge-Juan.Garcia-Garcia
2013-06-18 10:12 ` Ramkumar Ramachandra
2013-06-18 10:15 ` Mathieu Liénard--Mayor
2013-06-18 10:21 ` Ramkumar Ramachandra
2013-06-18 10:26 ` benoît person
2013-06-18 10:47 ` Ramkumar Ramachandra
2013-06-18 10:54 ` Mathieu Liénard--Mayor
2013-06-18 10:58 ` Ramkumar Ramachandra
2013-06-18 11:06 ` Matthieu Moy
2013-06-18 10:55 ` Ramkumar Ramachandra
2013-06-18 15:01 ` Junio C Hamano [this message]
2013-06-18 15:05 ` Matthieu Moy
2013-06-18 16:26 ` 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=7vip1b8nut.fsf@alter.siamese.dyndns.org \
--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=git@vger.kernel.org \
/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.