From: Junio C Hamano <firstname.lastname@example.org>
To: Jacob Keller <email@example.com>
Cc: Philip Oakley <firstname.lastname@example.org>, Git List <email@example.com>
Subject: Re: Can cc's be included in patches sent by send-email
Date: Thu, 11 Aug 2016 10:57:00 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CA+P7+xrBegRdS-HXi2SfO0Uu6N=gUVVp_F29GCb1rQn9cnxnHQ@mail.gmail.com> (Jacob Keller's message of "Thu, 11 Aug 2016 00:59:08 -0700")
Jacob Keller <email@example.com> writes:
> On Thu, Aug 11, 2016 at 12:58 AM, Jacob Keller <firstname.lastname@example.org> wrote:
>> On Thu, Aug 11, 2016 at 12:32 AM, Philip Oakley <email@example.com> wrote:
>>> While 'git send-email' can have multiple --cc="addressee" options on the
>>> command line, is it possible for the "cc:addressee<firstname.lastname@example.org>" to actually be
>>> included in the patches that are to be sent, so that different patches can
>>> have different addressee?
>>> The fortmat-patch can include appropriate from lines, so it feels as if the
>>> sender should be able to add cc: lines at the same place. Maybe its just
>>> part of th docs I've missed.
>> Yes, just put them in the body as tags below the signed-off-by. It
>> should be on by default unless you change supresscc or signedoffbycc
> See --suppress-cc or --signed-off-by-cc help in git help send-email.
Also, those who do not want to see Cc: in headers (like me) can
instead edit the header part of the format-patch output to add Cc:
lines and they should be picked up.
next prev parent reply other threads:[~2016-08-11 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 7:32 Can cc's be included in patches sent by send-email Philip Oakley
2016-08-11 7:58 ` Jacob Keller
2016-08-11 7:59 ` Jacob Keller
2016-08-11 17:57 ` Junio C Hamano [this message]
2016-08-11 17:58 ` Junio C Hamano
2016-08-11 19:11 ` Philip Oakley
2016-08-11 18:57 ` Philip Oakley
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).