git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Can cc's be included in patches sent by send-email

From
Philip Oakley <philipoakley@iee.org>
Date
Aug 11, 2016, 19:11 UTC
Message-ID
<75D9C1DBD21648F0B2511AA183C20CCD@PhilipOakley>
In-Reply-To
<xmqq4m6r2npv.fsf@gitster.mtv.corp.google.com>
From: "Junio C Hamano" <gitster@pobox.com>
Show 35 quoted lines
> Jacob Keller <jacob.keller@gmail.com> writes:
>
>> On Thu, Aug 11, 2016 at 12:58 AM, Jacob Keller <jacob.keller@gmail.com> 
>> wrote:
>>> On Thu, Aug 11, 2016 at 12:32 AM, Philip Oakley <philipoakley@iee.org> 
>>> 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.

Philip 
Previous: Junio C HamanoNext: Philip Oakley
Message 6 of 7 in “Can cc's be included in patches sent by send-email”
  1. Philip OakleyAug 11, 2016
  2. Jacob KellerAug 11, 2016
  3. Jacob KellerAug 11, 2016
  4. Junio C HamanoAug 11, 2016
  5. Junio C HamanoAug 11, 2016
  6. Philip OakleyAug 11, 2016
  7. Philip OakleyAug 11, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.