Re: [PATCH] docs: .gitignore parsing is to the top of the repo

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 6, 2021, 21:57 UTC
Message-ID: <xmqqk0m3gl6a.fsf@gitster.g>
In-Reply-To: <20210706205712.75270-1-andrew@furrypaws.ca>

Andrew Berry <andrew@furrypaws.ca> writes:

Show 13 quoted lines

>   * 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
> -   `.gitignore` file.  A project normally includes such
> -   `.gitignore` files in its repository, containing patterns for
> +   as the path, or in any parent directory (up to the top-level of the work
> +   tree), with patterns in the higher level files 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.

Line rewrapping makes it hard to see what actually got changed, but does this only move "(up to the top-level of the work tree)" around without anything else, as discussed?

If you do "toplevel" -> "top-level" while at it, perhaps we would want to correct "work tree" -> "working tree".

Looking better.

Thanks.