Andrew Berry <andrew@xxxxxxxxxxxx> writes: > The current documentation reads as if .gitignore files will be parsed in > every parent directory, and not until they reach a repository boundary. Hmph. While it is not adding an incorrect information to the documentation per-se, I am not sure if this is necessary to begin with. I would have thought that "up to the toplevel of the work tree" would be sufficiently clear where the upward traversal of the directories ends, i.e. at the repository boundary. > * Patterns read from a `.gitignore` file in the same directory > - as the path, or in any parent directory, with patterns in the > - higher level files (up to the toplevel of the work tree) being overridden > - by those in lower level files down to the directory containing the file. > - These patterns match relative to the location of the > + as the path, or in any parent directory in the same repository, with > + patterns in the higher level files (up to the toplevel of the work tree) > + being overridden by those in lower level files down to the directory > + containing the file. These patterns match relative to the location of the > `.gitignore` file. A project normally includes such > `.gitignore` files in its repository, containing patterns for > files generated as part of the project build.
