From: Junio C Hamano <gitster@pobox.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 1/2] git-send-email: two new options: to-cover, cc-cover
Date: Thu, 03 Apr 2014 11:31:51 -0700 [thread overview]
Message-ID: <xmqqa9c2qn6w.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1396548814-27278-1-git-send-email-mst@redhat.com> (Michael S. Tsirkin's message of "Thu, 3 Apr 2014 21:14:08 +0300")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> Allow extracting To/Cc addresses from cover letter.
Please say what you are doing with what you extract, which is the
more important part of the objective. Extracting is merely a step
to achieve that.
s/.$/, to be used as To/Cc addresses of the remainder of the series./
or something.
I think this will be a very handy feature.
If you have a series *and* you bothered to add To/Cc to the cover
letter, it is likely that you want all the messages read by these
people [*1*].
> @@ -1468,6 +1475,15 @@ foreach my $t (@files) {
> @to = (@initial_to, @to);
> @cc = (@initial_cc, @cc);
>
> + if ($message_num == 1) {
> + if (defined $cover_cc and $cover_cc) {
> + @initial_cc = @cc;
> + }
> + if (defined $cover_to and $cover_to) {
> + @initial_to = @to;
> + }
> + }
> +
What is stored away with this code to @initial_cc/to includes:
- what was given to @initial_cc/to before ll.1468-1469
- what was in @cc/to before ll.1468-1469
when we see the first message [*2*]. The former come from the
command line --to/--cc, and the latter comes from the header lines
of the first message. Am I reading the code correctly?
If that is the case, I think the updated code makes sense.
Thanks.
[Footnote]
*1* Allowing this to be disabled is also a good thing this patch
does. A 100 patch series that does a tree-wide clean-up may
have different set of people on To/Cc of individual patches, and
you may want the union of them on To/Cc on the cover letter, so
that a person may get the cover letter and a single patch that
relates to his area of expertise without having to see the
remainder.
*2* The first message may not necessarily be the cover letter. Is
there a reliable way to detect that? The user may want to send
out a series with only a few patches without any cover, and
taking To/Cc from the [PATCH 1/3] and propagating them to the
rest does not match what the documentation and the option name
claim to do.
next prev parent reply other threads:[~2014-04-03 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 18:14 [PATCH v2 1/2] git-send-email: two new options: to-cover, cc-cover Michael S. Tsirkin
2014-04-03 18:14 ` [PATCH v2 2/2] test/send-email: add to-cover test Michael S. Tsirkin
2014-04-03 18:44 ` Junio C Hamano
2014-04-03 18:31 ` Junio C Hamano [this message]
2014-04-27 18:36 ` [PATCH v2 1/2] git-send-email: two new options: to-cover, cc-cover Michael S. Tsirkin
2014-04-03 21:24 ` Eric Sunshine
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=xmqqa9c2qn6w.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mst@redhat.com \
/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.