From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Miklos Vajna" <vmiklos@frugalware.org>,
"Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] git-format-patch: add a new format.cc configuration variable
Date: Tue, 29 Apr 2008 13:21:36 -0400 [thread overview]
Message-ID: <76718490804291021m4d6827d3h522fe61b791ae067@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0804271252200.16320@eeepc-johanness>
On Sun, Apr 27, 2008 at 7:53 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
> On Sun, 27 Apr 2008, Miklos Vajna wrote:
>
> > On Sat, Apr 26, 2008 at 11:31:13PM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > I am wary... should this not be specific to send-email? IOW should
> > > format-patch not be left alone?
> >
> > 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.
You can do something like:
[sendemail]
cccmd = "sh -c 'echo address@example.com'"
j.
next prev parent reply other threads:[~2008-04-29 17:23 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
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 ` Jay Soffian [this message]
2008-04-27 0:14 ` [PATCH] git-format-patch: add a new format.cc " 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=76718490804291021m4d6827d3h522fe61b791ae067@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).