Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH v2 05/15] create-pull-request: provide an RFC mode via -c argument
Date: Mon, 16 May 2011 16:40:19 -0700	[thread overview]
Message-ID: <1305589219.1771.18.camel@vorpal.jf.intel.com> (raw)
In-Reply-To: <dfdc9f2a9d9eb8253b43f97fb52391bb96454155.1305584418.git.dvhart@linux.intel.com>

On Mon, 2011-05-16 at 15:26 -0700, Darren Hart wrote:
> Currently it is difficult to know if a pull request is being sent for review
> or just to be pulled.
> 
> Add a -c argument to add RFC to the subject prefix and a blurb requesting
> review to the cover letter.
> 
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Joshua Lock <josh@linux.intel.com>


> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> Cc: Saul Wold <sgw@linux.intel.com>
> Cc: Paul Eggleton <paul.eggleton@intel.com>
> Cc: Joshua Lock <josh@linux.intel.com>
> ---
>  scripts/create-pull-request |   24 ++++++++++++++++++++++--
>  1 files changed, 22 insertions(+), 2 deletions(-)
> 
> diff --git a/scripts/create-pull-request b/scripts/create-pull-request
> index 429421b..202d99d 100755
> --- a/scripts/create-pull-request
> +++ b/scripts/create-pull-request
> @@ -3,12 +3,14 @@ ODIR=pull-$$
>  RELATIVE_TO="master"
>  COMMIT_ID="HEAD"
>  PREFIX="PATCH"
> +RFC=0
>  
>  usage() {
>  CMD=$(basename $0)
>  cat <<EOM
>  Usage: $CMD [-h] [-o output_dir] [-m msg_body_file] [-s subject] [-r relative_to] [-i commit_id] -u remote -b branch
>    -b branch           Branch name in the specified remote
> +  -c                  Create an RFC (Request for Comment) patch series
>    -h                  Display this help message
>    -i commit_id        Ending commit (default: HEAD)
>    -m msg_body_file    The file containing a blurb to be inserted into the summary email
> @@ -27,11 +29,14 @@ EOM
>  }
>  
>  # Parse and validate arguments
> -while getopts "b:hi:m:o:p:r:s:u:" OPT; do
> +while getopts "b:chi:m:o:p:r:s:u:" OPT; do
>  	case $OPT in
>  	b)
>  		BRANCH="$OPTARG"
>  		;;
> +	c)
> +		RFC=1
> +		;;
>  	h)
>  		usage
>  		exit 0
> @@ -89,6 +94,10 @@ if [ -z "$BRANCH" ] || [ -z "$REMOTE_URL" ]; then
>  	exit 1
>  fi
>  
> +if [ $RFC -eq 1 ]; then
> +	PREFIX="RFC $PREFIX"
> +fi
> +
>  
>  # Set WEB_URL from known remotes
>  case "$REMOTE_URL" in
> @@ -125,7 +134,7 @@ git format-patch -M --subject-prefix="$PREFIX" -n -o $ODIR --thread=shallow --co
>  # Customize the cover letter
>  CL="$ODIR/0000-cover-letter.patch"
>  PM="$ODIR/pull-msg"
> -git request-pull $RELATIVE_TO $REMOTE_URL $COMMIT_ID > "$PM"
> +git request-pull $RELATIVE_TO $REMOTE_URL $COMMIT_ID >> "$PM"
>  if [ $? -ne 0 ]; then
>  	echo "ERROR: git request-pull reported an error"
>  	exit 1
> @@ -136,6 +145,17 @@ fi
>  sed -n "0,\#$REMOTE_URL# p" "$PM" | sed -i "/BLURB HERE/ r /dev/stdin" "$CL"
>  rm "$PM"
>  
> +# If this is an RFC, make that clear in the cover letter
> +if [ $RFC -eq 1 ]; then
> +(cat <<EOM
> +Please review the following changes for suitability for inclusion. If you have
> +any objections or suggestions for improvement, please respond to the patches. If
> +you agree with the changes, please provide your Acked-by.
> +
> +EOM
> +) | sed -i "/BLURB HERE/ r /dev/stdin" "$CL"
> +fi
> +
>  # Insert the WEB_URL if there is one
>  if [ -n "$WEB_URL" ]; then
>  	echo "  $WEB_URL" | sed -i "\#$REMOTE_URL# r /dev/stdin" "$CL"

-- 
Joshua Lock
        Yocto Project Build Monkey
        Intel Open Source Technology Centre




  reply	other threads:[~2011-05-16 23:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 22:25 [RFC PATCH v2 00/15] *-pull-request: cleanup and overhaul Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 01/15] create-pull-request: alphabetize arguments Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 02/15] create-pull-request: whitespace cleanup Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 03/15] create-pull-request: use git request-pull and arbitrary remotes Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 04/15] create-pull-request: rewrite known private URLs to public URLs Darren Hart
2011-05-16 23:40   ` Joshua Lock
2011-05-16 22:26 ` [RFC PATCH v2 05/15] create-pull-request: provide an RFC mode via -c argument Darren Hart
2011-05-16 23:40   ` Joshua Lock [this message]
2011-05-16 22:26 ` [RFC PATCH v2 06/15] send-pull-request: whitespace cleanup Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 07/15] send-pull-request: remove local mta support Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 08/15] send-pull-request: fix greedy auto-cc regex Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 09/15] send-pull-request: don't send all patches to everyone even with -a Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 10/15] send-pull-request: verify git sendemail config Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 11/15] create-pull-request: do not check certificate Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 12/15] create-pull-request: add GitHub remote support Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 13/15] create-pull-request: add untested oe repository support Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 14/15] send-pull-request: streamline git-send-email usage Darren Hart
2011-05-16 23:40   ` Joshua Lock
2011-05-17 17:05   ` Khem Raj
2011-05-17 17:38     ` Darren Hart
2011-05-16 22:26 ` [RFC PATCH v2 15/15] *pull-request: add copyright, license, and descriptions Darren Hart
2011-05-17 14:02 ` [RFC PATCH v2 00/15] *-pull-request: cleanup and overhaul Otavio Salvador
2011-05-17 19:02 ` Tom Rini
2011-05-20  0:46 ` Saul Wold

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=1305589219.1771.18.camel@vorpal.jf.intel.com \
    --to=josh@linux.intel.com \
    --cc=dvhart@linux.intel.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