public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] send-pull-request: add extra CC argument
Date: Mon,  4 Feb 2013 16:06:59 +0100	[thread overview]
Message-ID: <1359990419-20550-1-git-send-email-Martin.Jansa@gmail.com> (raw)

* useful e.g. when sending pull-request to release branch with extra CC
  for release maintainer

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 scripts/send-pull-request | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/scripts/send-pull-request b/scripts/send-pull-request
index 18a53c4..575549d 100755
--- a/scripts/send-pull-request
+++ b/scripts/send-pull-request
@@ -32,6 +32,7 @@ GITSOBCC="--suppress-cc=all"
 unset TO
 unset CC
 unset AUTO_CC
+unset EXTRA_CC
 
 usage()
 {
@@ -42,6 +43,7 @@ Usage: $(basename $0) [-h] [-a] [-c] [[-t email]...] -p pull-dir
 	       This option implies -c.
   -c           Expand the Cc list for the individual patches using the Cc and
                Signed-off-by lines from the same patch.
+  -C           Add extra CC to each email sent.
   -p pull-dir  Directory containing summary and patch files
   -t email     Explicitly add email to the recipients
 EOM
@@ -68,7 +70,7 @@ harvest_recipients()
 }
 
 # Parse and verify arguments
-while getopts "achp:t:" OPT; do
+while getopts "acC:hp:t:" OPT; do
 	case $OPT in
 	a)
 		AUTO=1
@@ -79,6 +81,9 @@ while getopts "achp:t:" OPT; do
 		AUTO=1
 		GITSOBCC="--signed-off-by-cc"
 		;;
+	C)
+		EXTRA_CC="$OPTARG"
+		;;
 	h)
 		usage
 		exit 0
@@ -149,15 +154,15 @@ fi
 export IFS=$','
 GIT_TO=$(for R in $TO; do echo -n "--to='$R' "; done)
 GIT_CC=$(for R in $AUTO_CC; do echo -n "--cc='$R' "; done)
+GIT_EXTRA_CC=$(for R in $EXTRA_CC; do echo -n "--cc='$R' "; done)
 unset IFS
 
-
 # Handoff to git-send-email. It will perform the send confirmation.
 PATCHES=$(echo $PDIR/*.patch)
 if [ $AUTO_CL -eq 1 ]; then
 	# Send the cover letter to every recipient, both specified as well as
 	# harvested. Then remove it from the patches list.
-	eval "git send-email $GIT_TO $GIT_CC --confirm=always --no-chain-reply-to --suppress-cc=all $CL"
+	eval "git send-email $GIT_TO $GIT_CC $GIT_EXTRA_CC --confirm=always --no-chain-reply-to --suppress-cc=all $CL"
 	if [ $? -eq 1 ]; then
 		echo "ERROR: failed to send cover-letter with automatic recipients."
 		exit 1
@@ -167,7 +172,7 @@ fi
 
 # Send the patch to the specified recipients and, if -c was specified, those git
 # finds in this specific patch.
-eval "git send-email $GIT_TO --confirm=always --no-chain-reply-to $GITSOBCC $PATCHES"
+eval "git send-email $GIT_TO $GIT_EXTRA_CC --confirm=always --no-chain-reply-to $GITSOBCC $PATCHES"
 if [ $? -eq 1 ]; then
 	echo "ERROR: failed to send patches."
 	exit 1
-- 
1.8.1.2




                 reply	other threads:[~2013-02-04 16:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1359990419-20550-1-git-send-email-Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox