From: Celeste Liu <coelacanthushex@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] doc: replace 3 dash with correct 2 dash in git-config(1)
Date: Fri, 23 Aug 2024 16:21:15 +0800 [thread overview]
Message-ID: <6c9f666e-12ad-4b67-a44a-3111686454f3@gmail.com> (raw)
In-Reply-To: <Zsgh4LacdOt8N69o@tanuki>
On 2024-08-23 13:45, Patrick Steinhardt wrote:
> On Fri, Aug 23, 2024 at 01:20:41AM +0800, Celeste Liu wrote:
>> Commit 4e51389000 (builtin/config: introduce "get" subcommand, 2024-05-06)
>> introduced this typo.
>
> We typically do not word the commit message as a continuation of the
> subject. The subject often becomes invisible in many contexts, so it is
> helpful if it can be read standalone while providing all of the context
> necessary. So mentioning what is wrong would be welcome here.
>
>> Fixes: 4e51389000 (builtin/config: introduce "get" subcommand, 2024-05-06)
>
> We do not use Fixes tags in the Git project.
>
>> Signed-off-by: Celeste Liu <CoelacanthusHex@gmail.com>
>> ---
>> Documentation/git-config.txt | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt
>> index 65c645d461..79360328aa 100644
>> --- a/Documentation/git-config.txt
>> +++ b/Documentation/git-config.txt
>> @@ -130,7 +130,7 @@ OPTIONS
>> --all::
>> With `get`, return all values for a multi-valued key.
>>
>> ----regexp::
>> +--regexp::
>> With `get`, interpret the name as a regular expression. Regular
>> expression matching is currently case-sensitive and done against a
>> canonicalized version of the key in which section and variable names
>
> This looks obviously correct to me.
>
> There's one more thing I noticed: the synopsis for `git config get` says
> `--regrexp=<regexp>`, which is clearly wrong. As you're already at it,
> would you mind including a second patch that corrects this?
I couldn't find this typo. Did I miss something? If something missed, please
tell me. I will include it in v3.
v2 has been sent.
>
> Thanks!
>
> Patrick
next prev parent reply other threads:[~2024-08-23 8:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 17:20 [PATCH] doc: replace 3 dash with correct 2 dash in git-config(1) Celeste Liu
2024-08-22 18:02 ` Junio C Hamano
2024-08-23 5:45 ` Patrick Steinhardt
2024-08-23 7:59 ` Celeste Liu
2024-08-23 8:21 ` Celeste Liu [this message]
2024-08-26 6:24 ` Patrick Steinhardt
2024-08-26 15:19 ` Junio C Hamano
2024-08-26 15:56 ` Celeste Liu
2024-08-26 17:19 ` Junio C Hamano
2024-08-26 17:31 ` [PATCH] git-config.1: --get-all description update Junio C Hamano
2024-08-26 17:32 ` [PATCH] doc: replace 3 dash with correct 2 dash in git-config(1) Junio C Hamano
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=6c9f666e-12ad-4b67-a44a-3111686454f3@gmail.com \
--to=coelacanthushex@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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).