mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Philip Oakley" <>
To: "Junio C Hamano" <>,
	"Jacob Keller" <>
Cc: "Git List" <>
Subject: Re: Can cc's be included in patches sent by send-email
Date: Thu, 11 Aug 2016 20:11:42 +0100	[thread overview]
Message-ID: <75D9C1DBD21648F0B2511AA183C20CCD@PhilipOakley> (raw)

From: "Junio C Hamano" <>
> Jacob Keller <> writes:
>> On Thu, Aug 11, 2016 at 12:58 AM, Jacob Keller <> 
>> wrote:
>>> On Thu, Aug 11, 2016 at 12:32 AM, Philip Oakley <> 
>>> wrote:
>>>> While 'git send-email' can have multiple --cc="addressee" options on 
>>>> the
>>>> command line, is it possible for the "cc:addressee<a@b.c>" 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
>>> configuration.
>>> Thanks,
>>> Jake
>> 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.
> --
When done via git gui, it looks like the Cc: is also included in the commit 
message (first initial tries)

I'd probably place them after a --- break so that they don't get into the 
applied commit message, but will carry around during my rebasing. I've still 
to test if it works though.


  parent reply	other threads:[~2016-08-11 19:11 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
2016-08-11 17:58       ` Junio C Hamano
2016-08-11 19:11       ` Philip Oakley [this message]
2016-08-11 18:57     ` Philip Oakley

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75D9C1DBD21648F0B2511AA183C20CCD@PhilipOakley \ \ \ \ \

* 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).