From: "Jonas Wunderlich via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Jonas Wunderlich <git@03j.de>, Jonas Wunderlich <git@03j.de>
Subject: [PATCH] documentation: camel case of config option, and "no" instead of "false"
Date: Tue, 12 Mar 2024 21:34:11 +0000 [thread overview]
Message-ID: <pull.1686.git.git.1710279251901.gitgitgadget@gmail.com> (raw)
From: Jonas Wunderlich <git@03j.de>
The `status.showUntrackedFiles` config option only accepts the values "no",
"normal" or "all", but not as this part of the man page suggested "false".
Signed-off-by: Jonas Wunderlich <git@03j.de>
---
documentation: camel case of config option, and "no" instead of "false"
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1686%2Fjonas-w%2Fpatch-1-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1686/jonas-w/patch-1-v1
Pull-Request: https://github.com/git/git/pull/1686
Documentation/git-status.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
index 4dbb88373bc..b0f36fabfb3 100644
--- a/Documentation/git-status.txt
+++ b/Documentation/git-status.txt
@@ -472,7 +472,7 @@ again, because your configuration may already be caching `git status`
results, so it could be faster on subsequent runs.
* The `--untracked-files=no` flag or the
- `status.showUntrackedfiles=false` config (see above for both):
+ `status.showUntrackedFiles=no` config (see above for both):
indicate that `git status` should not report untracked
files. This is the fastest option. `git status` will not list
the untracked files, so you need to be careful to remember if
base-commit: 945115026aa63df4ab849ab14a04da31623abece
--
gitgitgadget
next reply other threads:[~2024-03-12 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 21:34 Jonas Wunderlich via GitGitGadget [this message]
2024-03-13 16:14 ` [PATCH] documentation: camel case of config option, and "no" instead of "false" 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=pull.1686.git.git.1710279251901.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@03j.de \
--cc=git@vger.kernel.org \
/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).