From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>, Celeste Liu <coelacanthushex@gmail.com>
Subject: [PATCH] git-config.1: --get-all description update
Date: Mon, 26 Aug 2024 10:31:19 -0700 [thread overview]
Message-ID: <xmqqplpvjimw.fsf_-_@gitster.g> (raw)
In-Reply-To: <xmqq34mrkxre.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 26 Aug 2024 10:19:17 -0700")
"git config --get-all foo.bar" shows all values for the foo.bar
variable, but does not give the variable name in each output entry.
Hence it is equivalent to "git config get --all foo.bar", without
"--show-names", in the more modern syntax.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
diff --git i/Documentation/git-config.txt w/Documentation/git-config.txt
index 65c645d461..1ee5c89ba2 100644
--- i/Documentation/git-config.txt
+++ w/Documentation/git-config.txt
@@ -309,7 +309,7 @@ recommended to migrate to the new syntax.
Replaced by `git config get [--value=<pattern>] <name>`.
--get-all <name> [<value-pattern>]::
- Replaced by `git config get [--value=<pattern>] --all --show-names <name>`.
+ Replaced by `git config get [--value=<pattern>] --all <name>`.
--get-regexp <name-regexp>::
Replaced by `git config get --all --show-names --regexp <name-regexp>`.
next prev parent reply other threads:[~2024-08-26 17:31 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
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 ` Junio C Hamano [this message]
2024-08-26 17:32 ` 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=xmqqplpvjimw.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).