From: Junio C Hamano <gitster@pobox.com>
To: Celeste Liu <coelacanthushex@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH] doc: replace 3 dash with correct 2 dash in git-config(1)
Date: Thu, 22 Aug 2024 11:02:09 -0700 [thread overview]
Message-ID: <xmqqseuwqvvi.fsf@gitster.g> (raw)
In-Reply-To: <20240822172042.54065-1-CoelacanthusHex@gmail.com> (Celeste Liu's message of "Fri, 23 Aug 2024 01:20:41 +0800")
Celeste Liu <coelacanthushex@gmail.com> writes:
> Commit 4e51389000 (builtin/config: introduce "get" subcommand, 2024-05-06)
> introduced this typo.
>
> Fixes: 4e51389000 (builtin/config: introduce "get" subcommand, 2024-05-06)
> 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
Looks obviously correct. Thanks.
next prev parent reply other threads:[~2024-08-22 18:02 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 [this message]
2024-08-23 5:45 ` Patrick Steinhardt
2024-08-23 7:59 ` Celeste Liu
2024-08-23 8:21 ` Celeste Liu
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=xmqqseuwqvvi.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=coelacanthushex@gmail.com \
--cc=git@vger.kernel.org \
--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).