Skip to contentSkip to conversation

doc: replace 3 dash with correct 2 dash in git-config(1)

PATCH In review Celeste Liu 2 participants 2 messages Aug 23, 2024 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 doc: replace 3 dash with correct 2 dash in git-config(1)

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.

---
Changes in v2:
- Clarify typo details.
- Remove Fixes tag because Git doesn't use it.
- Link to v1: https://lore.kernel.org/git/[email protected]/

---
 Documentation/git-config.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/git-config.txt +1 -1
index 65c645d461..79360328aa 100644
@@ -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,

Signature · 1 line
Celeste Liu <[email protected]>
#1 lore raw
Quoted 10 lines · Celeste Liu

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.

---
Changes in v2:
- Clarify typo details.
- Remove Fixes tag because Git doesn't use it.
- Link to v1: https://lore.kernel.org/git/[email protected]/

Thanks. I'll do "typo, it" -> "typo. It" while queuing.

I couldn't spot the "regrexp", either, by the way.

Quoted 23 lines
---
 Documentation/git-config.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/git-config.txt +1 -2
index 65c645d461..79360328aa 100644
@@ -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,