All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Jacob Keller" <jacob.keller@gmail.com>
Cc: "Git List" <git@vger.kernel.org>
Subject: Re: Can cc's be included in patches sent by send-email
Date: Thu, 11 Aug 2016 19:57:46 +0100	[thread overview]
Message-ID: <4AF832719F594FF487BFEFBC9D289942@PhilipOakley> (raw)
In-Reply-To: CA+P7+xrBegRdS-HXi2SfO0Uu6N=gUVVp_F29GCb1rQn9cnxnHQ@mail.gmail.com

From: "Jacob Keller" <jacob.keller@gmail.com>
> 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.
>
> Thanks,
> Jake

Thanks,
I'll look at that. It wasn't immediately obvious what to do.

Philip 


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

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=4AF832719F594FF487BFEFBC9D289942@PhilipOakley \
    --to=philipoakley@iee.org \
    --cc=git@vger.kernel.org \
    --cc=jacob.keller@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.