From: Thomas Monjalon <thomas@monjalon.net>
To: Ciara Power <ciara.power@intel.com>
Cc: john.mcnamara@intel.com, marko.kovacevic@intel.com,
ferruh.yigit@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/3] devtools: standardize script arguments
Date: Wed, 17 Jun 2020 11:40:16 +0200 [thread overview]
Message-ID: <13848042.yhPDGZm4c5@thomas> (raw)
In-Reply-To: <20200602135319.21457-2-ciara.power@intel.com>
02/06/2020 15:53, Ciara Power:
> This patch modifies the arguments expected by the check-git-log script,
> to match the format of arguments for the checkpatches script. Both
> scripts now take certain argument options in the same format, making
> them easier to use.
> e.g. Both now take a commit ID range by "-r <range>"
>
> The checkpatches help print is also updated to include the "-h" option.
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> ---
> v3:
> - Reworded check-git-log help text example.
> - Added comment to indicate new and old format argument parsing.
> v2: Added exit 0 after print usage.
> ---
> --- a/devtools/check-git-log.sh
> +++ b/devtools/check-git-log.sh
> + The git commits to be checked can be specified as a "git log" option,
> + by latest git commits limited with -n option, or commits in the git
> + range specified with -r option.
> + e.g. To check only the last commit, ‘-n1’ or ‘-r@~..’ is used.
> + When no parameter is provided, script will use range starting from
> + origin/master to HEAD.
I suggest this shorter sentence:
If no range provided, default is origin/master..HEAD.
> +# The script caters for two formats, the new preferred format, and the old
> +# format to ensure backward compatibility.
> +# The new format is aligned with the format of the checkpatches script,
> +# and allows for specifying the patches to check by passing -nX or -r range.
> +# e.g. To check only the last commit, ‘-n1’ or ‘-r@~..’ is used.
This example line is useless here.
> +# The old format allows for specifying patches by passing -X or range
> +# as the first argument.
> +# e.g. To check only the last commit, '-1' or '@~..' is used as first argument.
This example line is useless here.
next prev parent reply other threads:[~2020-06-17 9:40 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
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 [this message]
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=13848042.yhPDGZm4c5@thomas \
--to=thomas@monjalon.net \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.