From e750951e74fc3fc2b40a8601b70cdf6e69ec6cf2 Mon Sep 17 00:00:00 2001 From: Elijah Newren Date: Fri, 13 Jan 2023 04:41:54 +0000 Subject: [PATCH] ls-files: guide folks to --exclude-standard over other --exclude* options Signed-off-by: Elijah Newren Signed-off-by: Junio C Hamano --- Documentation/git-ls-files.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-files.txt index 3886d58d17..1abdd3c21c 100644 --- a/Documentation/git-ls-files.txt +++ b/Documentation/git-ls-files.txt @@ -119,7 +119,8 @@ OPTIONS --exclude-per-directory=:: Read additional exclude patterns that apply only to the - directory and its subdirectories in . + directory and its subdirectories in . Deprecated; use + --exclude-standard instead. --exclude-standard:: Add the standard Git exclusions: .git/info/exclude, .gitignore @@ -291,7 +292,9 @@ traversing the directory tree and finding files to show when the flags --others or --ignored are specified. linkgit:gitignore[5] specifies the format of exclude patterns. -These exclude patterns come from these places, in order: +Generally, you should just use --exclude-standard, but for historical +reasons the exclude patterns can be specified from the following +places, in order: 1. The command-line flag --exclude= specifies a single pattern. Patterns are ordered in the same order