From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] git-send-email: add a new sendemail.cc configuration variable
Date: Sun, 27 Apr 2008 13:26:48 -0700 [thread overview]
Message-ID: <7vprsbf3hz.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080427121458.GU4012@genesis.frugalware.org> (Miklos Vajna's message of "Sun, 27 Apr 2008 14:14:58 +0200")
Miklos Vajna <vmiklos@frugalware.org> writes:
> Some projects prefer to always CC patches to a given mailing list. In
> these cases, it's handy to configure that address once.
>
> Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
> ---
>
> On Sun, Apr 27, 2008 at 12:53:34PM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>> > Yes and no. :-) I first searched for a --cc option in send-email,
>> > then
>> > realized that only format-patch has one.
>>
>> You are completely correct, sorry. Hmm. I would have preferred
>> send-email inserting that header, oh well.
>
> Heh, no. git-send-email has a --cc option as well, just it was not
> configurable. Here is a one-liner which does the trick.
Thanks, the idea makes sense.
Tests?
next prev parent reply other threads:[~2008-04-27 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 21:19 [PATCH] git-format-patch: add a new format.cc configuration variable Miklos Vajna
2008-04-26 22:31 ` Johannes Schindelin
2008-04-26 23:27 ` Miklos Vajna
2008-04-27 11:53 ` Johannes Schindelin
2008-04-27 12:14 ` [PATCH] git-send-email: add a new sendemail.cc " Miklos Vajna
2008-04-27 20:26 ` Junio C Hamano [this message]
2008-04-27 22:42 ` Miklos Vajna
2008-04-27 23:51 ` Jeff King
2008-04-29 10:56 ` [PATCH] Add tests for " Miklos Vajna
2008-04-29 17:21 ` [PATCH] git-format-patch: add a new format.cc " Jay Soffian
2008-04-27 0:14 ` Junio C Hamano
2008-04-27 5:09 ` [PATCH] bash: Add long option completion for 'git send-email' Teemu Likonen
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=7vprsbf3hz.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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 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).