From: Celeste Liu <coelacanthushex@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
Patrick Steinhardt <ps@pks.im>,
Celeste Liu <CoelacanthusHex@gmail.com>
Subject: [PATCH v2] doc: replace 3 dash with correct 2 dash in git-config(1)
Date: Fri, 23 Aug 2024 16:21:08 +0800 [thread overview]
Message-ID: <20240823-fix-doc-regexp-v2-1-e4eafdd60378@gmail.com> (raw)
Commit 4e51389000 (builtin/config: introduce "get" subcommand, 2024-05-06)
introduced this typo, it uses 3 dash for regexp argument instead of
correct 2 dash.
Signed-off-by: Celeste Liu <CoelacanthusHex@gmail.com>
---
Changes in v2:
- Clarify typo details.
- Remove Fixes tag because Git doesn't use it.
- Link to v1: https://lore.kernel.org/git/20240822172042.54065-1-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
---
base-commit: 3a7362eb9fad0c4838f5cfaa95ed3c51a4c18d93
change-id: 20240823-fix-doc-regexp-727a82281737
Best regards,
--
Celeste Liu <CoelacanthusHex@gmail.com>
next reply other threads:[~2024-08-23 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 8:21 Celeste Liu [this message]
2024-08-23 13:12 ` [PATCH v2] 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=20240823-fix-doc-regexp-v2-1-e4eafdd60378@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).