From: Jani Nikula <jani.nikula@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH maintainer-tools] frob-patch-rank: A little script to batch renaming patch files
Date: Tue, 10 Jun 2014 14:57:20 +0300 [thread overview]
Message-ID: <87a99lc6zj.fsf@intel.com> (raw)
In-Reply-To: <1402400719-21641-1-git-send-email-damien.lespiau@intel.com>
On Tue, 10 Jun 2014, Damien Lespiau <damien.lespiau@intel.com> wrote:
> The "usage" text should explain it all. I found, in my quilt series
> handling endeavours, that I wanted to be able to shift the prefix
> numbers of a patch series.
>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
> ---
> frob-patch-rank | 47 +++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100755 frob-patch-rank
>
> diff --git a/frob-patch-rank b/frob-patch-rank
> new file mode 100755
> index 0000000..4be42e5
> --- /dev/null
> +++ b/frob-patch-rank
> @@ -0,0 +1,47 @@
> +#!/bin/sh
> +set -e
> +
> +script=$(basename $0)
> +[ $# -ge 3 ] || {
> + echo "Usage: $script start end expr"
> + echo
> + echo " Frob patches."
> + echo
> + echo " This tiny script renames \"git format-patch\" patches by executing 'expr'"
> + echo " on the number that prefix the patch file, but only if the patch file name "
> + echo " starts with a number in ['start','end']."
> + echo
> + echo "Examples:"
> + echo " $ ls *patch"
> + echo " 0008-Super-patch.patch"
> + echo " 0009-Mega-patch.patch"
> + echo " $ $script 8 9 -7"
> + echo " $ ls *patch"
> + echo " 0001-Super-patch.patch"
> + echo " 0002-Mega-patch.patch"
> + echo
> + echo "Examples:"
> + echo " $ ls *patch"
> + echo " 0117-Super-patch.patch"
> + echo " 0118-Mega-patch.patch"
> + echo " $ $script 8 9 +900 -17"
I was scratching my head for a while with this example. It's wrong isn't
it?
The help could benefit from a "here" document.
> + echo " $ ls *patch"
> + echo " 1000-Super-patch.patch"
> + echo " 1001-Mega-patch.patch"
> + exit 1
> +}
> +
> +start=$1
> +end=$2
> +shift 2
> +op=$*
> +
> +for i in $(seq $start $end); do
> + prefix=$(printf "%04d" $i)
> + for f in $(ls $prefix-*.patch); do
> + base=${f#$prefix-}
> + ((n=$i $op))
> + new_prefix=$(printf "%04d" $n)
> + mv $prefix-$base $new_prefix-$base
mv -i just in case?
BR,
Jani.
> + done
> +done
> --
> 1.8.3.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-06-10 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 11:45 [PATCH maintainer-tools] frob-patch-rank: A little script to batch renaming patch files Damien Lespiau
2014-06-10 11:57 ` Jani Nikula [this message]
2014-06-10 12:46 ` [PATCH v2 " Damien Lespiau
2014-06-13 10:00 ` Jani Nikula
2014-06-16 23:36 ` [PATCH v3 " Damien Lespiau
2014-06-17 10:09 ` Jani Nikula
2014-06-17 10:23 ` [PATCH v4 " Damien Lespiau
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=87a99lc6zj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.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