From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
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>
Subject: Re: [PATCH 2/2] send-email: allow multiple emails using --cc, --to and --bcc
Date: Mon, 01 Jun 2015 17:12:05 +0200 [thread overview]
Message-ID: <vpqa8wjcvju.fsf@anie.imag.fr> (raw)
In-Reply-To: <1433168042-28269-2-git-send-email-remi.lespinet@ensimag.grenoble-inp.fr> (Remi Lespinet's message of "Mon, 1 Jun 2015 16:14:02 +0200")
Remi Lespinet <remi.lespinet@ensimag.grenoble-inp.fr> writes:
> Remove the limitation imposed by 79ee555b (Check and document the
> options to prevent mistakes, 2006-06-21) which rejected every argument
> with comma in --cc, --to and --bcc
Missing "." at the end of sentence.
> -The --bcc option must be repeated for each user you want on the bcc list.
> +Addresses containing commas ("Foo, Bar" <foobar@example.com>) are not
> +currently supported.
> ++
> +This option may be specified multiple times
Likewise (more instances in the patch).
> +test_expect_success $PREREQ 'setup expected-list' '
> + git send-email \
> + --dry-run \
> + --from="Example <from@example.com>" \
> + --to="to1@example.com" \
> + --to="to2@example.com" \
> + --to="to3@example.com" \
> + --cc="cc1@example.com" \
> + --cc="Cc 1 <cc1@example.com>" \
> + --cc="Cc 2 <cc2@example.com>" \
> + --bcc="bcc1@example.com" \
> + --bcc="bcc2@example.com" \
> + 0001-add-master.patch | replace_variable_fields \
Tab after |. Not really serious, but why not a space?
> + >expected-list
> +'
> +
> +test_expect_success $PREREQ 'use email list in --cc --to and --bcc' '
> + git send-email \
> + --dry-run \
> + --from="Example <from@example.com>" \
> + --to="to1@example.com, to2@example.com" \
> + --to="to3@example.com" \
> + --cc="cc1@example.com, Cc 1 <cc1@example.com>" \
> + --cc="Cc 2 <cc2@example.com>" \
> + --bcc="bcc1@example.com, bcc2@example.com" \
> + 0001-add-master.patch | replace_variable_fields \
> + >actual-list &&
You may drop the space between TAB and >.
I would group the tests: the 'setup' is only used to generate
expected-list which is used only in the second test, so one is not
useful without the other (we commonly have a 'setup ...' test which sets
up something used by several other tests).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-06-01 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 14:14 [PATCH 1/2] t9001-send-email: create a function replacing variable fields Remi Lespinet
2015-06-01 14:14 ` [PATCH 2/2] send-email: allow multiple emails using --cc, --to and --bcc Remi Lespinet
2015-06-01 15:12 ` Matthieu Moy [this message]
2015-06-01 15:19 ` Junio C Hamano
2015-06-01 16:52 ` Junio C Hamano
2015-06-02 8:26 ` Rémi Lespinet
2015-06-02 17:19 ` 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=vpqa8wjcvju.fsf@anie.imag.fr \
--to=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.