Show 31 quoted lines
> 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>
> ---
> Documentation/gitignore.txt | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/gitignore.txt b/Documentation/gitignore.txt
> index 53e7d5c914..534cda5747 100644
> --- a/Documentation/gitignore.txt
> +++ b/Documentation/gitignore.txt
> @@ -27,10 +27,10 @@ precedence, the last matching pattern decides the outcome):
> them.
>
> * 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.