Re: [PATCH v2] t/perf/run: Use proper "--get-regexp", not "--get-regex"
- Date: Sun, 3 Jun 2018 09:36:40 -0400 (EDT)
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- Subject: Re: [PATCH v2] t/perf/run: Use proper "--get-regexp", not "--get-regex"
On Sun, 3 Jun 2018, Thomas Gummerer wrote:
> > 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.
argh, i actually know that, i just screwed up.
> 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.
the actual rationale for v2 was in the subject, i originally put
just "get-regex" rather then "--get-regex"; i resubmitted for
Robert P. J. Day Ottawa, Ontario, CANADA