From: Christian Biesinger <cbiesinger@web.de>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Ryan Anderson <ryan@michonline.com>,
Greg Kroah-Hartman <greg@kroah.com>
Subject: Re: [PATCH] Don't send copies to the From: address
Date: Sat, 11 Feb 2006 13:31:13 +0100 [thread overview]
Message-ID: <43EDD911.3030003@web.de> (raw)
In-Reply-To: <7vk6c2sg66.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I cannot speak for Ryan or Greg, but I think the script
> deliberately does this to support this workflow:
Yeah, I suspected that this was the usecase. I don't think the patch
breaks that, it just compares those addresses to $from, i.e. the address
from which the email is sent.
> Me, personally I do not like CC: to people on the signed-off-by
> list, but dropping a note to From: person makes perfect sense to
> me, if it is to notify the progress of the patch.
I guess my description was a bit ambiguous, I didn't mean From: as in
"author of the patch", but instead From: as in "the email header for the
sender of the message", that is, the person who invokes git-send-email.
> What you are after _might_ be not CC'ing it if it was your own
> patch. Maybe something like this would help, but even if that
> is the case I suspect many people want to CC herself so it needs
> to be an optional feature.
So a new --no-cc-self option?
> - $cc = join(", ", unique_email_list(@cc));
> + $cc = join(", ", unique_email_list(grep { $_ ne $from } @cc));
This seems to be basically the same as what my patch does, except that
your way seems better :-)
next prev parent reply other threads:[~2006-02-11 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 2:47 [PATCH] Don't send copies to the From: address Christian Biesinger
2006-02-11 3:55 ` Junio C Hamano
2006-02-11 4:52 ` Greg KH
2006-02-11 12:33 ` Christian Biesinger
2006-02-11 12:31 ` Christian Biesinger [this message]
2006-02-13 7:20 ` Ryan Anderson
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=43EDD911.3030003@web.de \
--to=cbiesinger@web.de \
--cc=git@vger.kernel.org \
--cc=greg@kroah.com \
--cc=junkio@cox.net \
--cc=ryan@michonline.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 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).