mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Philip Oakley" <>
To: "Git List" <>
Subject: Can cc's be included in patches sent by send-email
Date: Thu, 11 Aug 2016 08:32:08 +0100	[thread overview]
Message-ID: <D8F2D8316A4C4E198C6847C1165A8811@PhilipOakley> (raw)

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.

This is for the workflow where the patch series (including cover letter) is 
reviewed before send-email is invoked to send to all adressees.


             reply	other threads:[~2016-08-11  7:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11  7:32 Philip Oakley [this message]
2016-08-11  7:58 ` Can cc's be included in patches sent by send-email 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

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=D8F2D8316A4C4E198C6847C1165A8811@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).