git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] t/perf/run: Use proper "--get-regexp", not "--get-regex"

From
Philip Oakley <philipoakley@iee.org>
Date
Jun 3, 2018, 15:33 UTC
Message-ID
<0AE4648A05C445FBA049864F455B35A7@PhilipOakley>
In-Reply-To
<alpine.LFD.2.21.1806030935010.21364@localhost.localdomain>
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
Show 19 quoted lines
> 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.
it's in `git help cli`:

many commands allow a long option --option to be abbreviated only to their unique prefix (e.g. if there is no other option whose name begins with opt, you may be able to spell --opt to invoke the --option flag), but you should fully spell them out when writing your scripts;

It's a worthwile read, even if the man page isn't flagged up that often.
Show 18 quoted lines
>>
>> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>> >
>> > ---
>>
>> 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
> consistency.
>

-- Philip

Previous: Robert P. J. DayNext: Robert P. J. Day
Message 4 of 6 in “t/perf/run: Use proper "--get-regexp", not "--get-regex"”
  1. t/perf/run: Use proper "--get-regexp", not "--get-regex"Robert P. J. Day, Jun 3, 2018
  2. Thomas GummererJun 3, 2018
  3. Robert P. J. DayJun 3, 2018
  4. Philip OakleyJun 3, 2018
  5. Robert P. J. DayJun 4, 2018
  6. Junio C HamanoJun 4, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.