> Subject: [PATCH v2] t/perf/run: Use proper "--get-regexp", not
micronit: we prefer starting with a lowercase letter after the "area:"
prefix in commit messages. Junio can probably fix that while
queuing, so no need to resend.
On 06/03, Robert P. J. Day wrote:
>
> Even though "--get-regex" appears to work with "git config", the
> clear standard is to spell out the action in full.
--get-regex works as the parse-option API allows abbreviations of the
full option to be specified as long as the abbreviation is
unambiguos. I don't know if this is documented anywhere other than
'Documentation/technical/api-parse-options.txt' though.
> Signed-off-by: Robert P. J. Day <rpjday@xxxxxxxxxxxxxx>
>
> ---
It took me a bit to figure out why there is a v2, and what changed
between the versions. This space after the '---' would be a good
place to describe that to help reviewers.
For others that are curious, it seems like the word "clear" was added
in the commit message.
The change itself looks good to me.
> this is the only occurrence i saw of this in the entire code base, so
> it seemed worth tweaking just for consistency.
>
> diff --git a/t/perf/run b/t/perf/run
> index 9aaa733c7..fb5753ea2 100755
> --- a/t/perf/run
> +++ b/t/perf/run
> @@ -110,7 +110,7 @@ run_dirs () {
> get_subsections () {
> section="$1"
> test -z "$GIT_PERF_CONFIG_FILE" && return
> - git config -f "$GIT_PERF_CONFIG_FILE" --name-only --get-regex "$section\..*\.[^.]+" |
> + git config -f "$GIT_PERF_CONFIG_FILE" --name-only --get-regexp "$section\..*\.[^.]+" |
> sed -e "s/$section\.\(.*\)\..*/\1/" | sort | uniq
> }
>
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca/dokuwiki
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
