From: Junio C Hamano <gitster@pobox.com>
To: Andrew Berry <andrew@furrypaws.ca>
Cc: git@vger.kernel.org, bagasdotme@gmail.com
Subject: Re: [PATCH] docs: .gitignore parsing is to the top of the repo
Date: Tue, 06 Jul 2021 14:55:28 -0700 [thread overview]
Message-ID: <xmqqo8bfgl9r.fsf@gitster.g> (raw)
In-Reply-To: <20210706205439.75015-1-andrew@furrypaws.ca> (Andrew Berry's message of "Tue, 6 Jul 2021 16:54:39 -0400")
Andrew Berry <andrew@furrypaws.ca> writes:
> 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.
Sent a wrong/stale patch?
prev parent reply other threads:[~2021-07-06 21:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 22:20 [PATCH] docs: .gitignore in parents is current repo only Andrew Berry
2021-07-03 0:06 ` Junio C Hamano
2021-07-03 0:21 ` Bagas Sanjaya
2021-07-05 17:30 ` Andrew Berry
2021-07-05 19:59 ` Junio C Hamano
2021-07-05 23:50 ` Andrew Berry
2021-07-06 16:18 ` Junio C Hamano
2021-07-06 20:54 ` [PATCH] docs: .gitignore parsing is to the top of the repo Andrew Berry
2021-07-06 20:57 ` Andrew Berry
2021-07-06 21:57 ` Junio C Hamano
2021-07-07 0:18 ` Junio C Hamano
2021-07-07 0:32 ` Andrew Berry
2021-07-07 1:20 ` Junio C Hamano
2021-07-18 14:12 ` Andrew Berry
2021-07-19 18:36 ` Junio C Hamano
2021-07-06 21:55 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo8bfgl9r.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=andrew@furrypaws.ca \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).