From: Thomas Monjalon <thomas@monjalon.net>
To: Ciara Power <ciara.power@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] devtools: standardize script arguments
Date: Sat, 22 Feb 2020 21:53:02 +0100 [thread overview]
Message-ID: <3605642.fW5hKsROvD@xps> (raw)
In-Reply-To: <20200128150256.14339-2-ciara.power@intel.com>
Hi,
Thanks for improving tooling.
28/01/2020 16:02, Ciara Power:
> range=${1:-origin/master..}
If doing a real option management, range should be the remaining argument
after option parsing.
> +if [ "$range" = '--help' ] ; then
> + print_usage
Missing "exit 0" after usage.
> # convert -N to HEAD~N.. in order to comply with git-log-fixes.sh getopts
> -if printf -- $range | grep -q '^-[0-9]\+' ; then
> - range="HEAD$(printf -- $range | sed 's,^-,~,').."
> +elif printf -- "$range" | grep -q '^-[0-9]\+' ; then
> + range="HEAD$(printf -- "$range" | sed 's,^-,~,').."
getopts won't be called if $1 starts with -N.
I think it would be cleaner to handle this in "?" case below.
> +else
> + while getopts hr:n: ARG ; do
> + case $ARG in
> + n ) range="HEAD~$OPTARG.." ;;
> + r ) range=$OPTARG ;;
-r is not a git-log option.
Please handle it without the need for -r.
> + h ) print_usage ; exit 0 ;;
> + ? ) print_usage ; exit 1 ;;
> + esac
> + done
> + shift $(($OPTIND - 1))
next prev parent reply other threads:[~2020-02-22 20:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:02 [dpdk-dev] [PATCH 0/2] standardize devtools check scripts Ciara Power
2020-01-28 15:02 ` [dpdk-dev] [PATCH 1/2] devtools: standardize script arguments Ciara Power
2020-01-28 15:40 ` Ferruh Yigit
2020-02-22 20:53 ` Thomas Monjalon [this message]
2020-03-31 13:11 ` Power, Ciara
2020-01-28 15:02 ` [dpdk-dev] [PATCH 2/2] devtools: added stats print Ciara Power
2020-01-28 15:41 ` Ferruh Yigit
2020-02-22 20:55 ` Thomas Monjalon
2020-05-06 9:55 ` [dpdk-dev] [PATCH v2 0/2] standardize devtools check scripts Ciara Power
2020-05-06 9:55 ` [dpdk-dev] [PATCH v2 1/2] devtools: standardize script arguments Ciara Power
2020-05-24 20:57 ` Thomas Monjalon
2020-05-28 14:37 ` Power, Ciara
2020-05-28 15:03 ` Thomas Monjalon
2020-05-06 9:55 ` [dpdk-dev] [PATCH v2 2/2] devtools: added stats print Ciara Power
2020-06-02 13:53 ` [dpdk-dev] [PATCH v3 0/3] standardize devtools check scripts Ciara Power
2020-06-02 13:53 ` [dpdk-dev] [PATCH v3 1/3] devtools: standardize script arguments Ciara Power
2020-06-17 9:40 ` Thomas Monjalon
2020-06-02 13:53 ` [dpdk-dev] [PATCH v3 2/3] devtools: added stats print Ciara Power
2020-06-02 13:53 ` [dpdk-dev] [PATCH v3 3/3] doc/guides: updated script usage for checking patches Ciara Power
2020-06-03 15:50 ` Ferruh Yigit
2020-06-17 9:46 ` Thomas Monjalon
2020-06-23 9:29 ` [dpdk-dev] [PATCH v4 0/2] standardize devtools check scripts Ciara Power
2020-06-23 9:29 ` [dpdk-dev] [PATCH v4 1/2] devtools: standardize script arguments Ciara Power
2020-06-23 9:29 ` [dpdk-dev] [PATCH v4 2/2] devtools: added stats print Ciara Power
2020-07-30 22:50 ` Thomas Monjalon
2020-07-30 22:52 ` [dpdk-dev] [PATCH v4 0/2] standardize devtools check scripts Thomas Monjalon
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=3605642.fW5hKsROvD@xps \
--to=thomas@monjalon.net \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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 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 NNTP newsgroup(s).