docs: .gitignore parsing is to the top of the repo
The current documentation reads as if .gitignore files will be parsed in every parent directory, and not until they reach a repository boundary. This clarifies the current behaviour. As well, this corrects 'toplevel' to 'top-level', matching usage for 'top-level domain'. Signed-off-by: Andrew Berry <andrew@furrypaws.ca> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Andrew Berry committed
Jul 6, 2021 at 16:57 UTC
e04170697a2848189492d53c7b3aab59c32d044f
1 file changed
+5
-6
Documentation/gitignore.txt
+5
-6
@@ -27,12 +27,11 @@ precedence, the last matching pattern decides the outcome):
27
them.
28
29
* Patterns read from a `.gitignore` file in the same directory
30
- as the path, or in any parent directory, with patterns in the
31
- higher level files (up to the toplevel of the work tree) being overridden
32
- by those in lower level files down to the directory containing the file.
33
- These patterns match relative to the location of the
34
- `.gitignore` file. A project normally includes such
35
- `.gitignore` files in its repository, containing patterns for
30
+ as the path, or in any parent directory (up to the top-level of the working
31
+ tree), with patterns in the higher level files being overridden by those in
32
+ lower level files down to the directory containing the file. These patterns
33
+ match relative to the location of the `.gitignore` file. A project normally
34
+ includes such `.gitignore` files in its repository, containing patterns for
35
files generated as part of the project build.
36
37
* Patterns read from `$GIT_DIR/info/exclude`.