Re: [PATCH] docs: .gitignore in parents is current repo only
- From
Andrew Berry <andrew@furrypaws.ca>
- Date
- Jul 5, 2021, 17:30 UTC
- Message-ID
- <889D9AD1-1114-49B4-ADB0-BF78160743E4@furrypaws.ca>
- In-Reply-To
- <b9da43a8-897b-7cce-ecbc-ea56078f0f09@gmail.com>
On 2 Jul 2021, at 20:06, Junio C Hamano wrote:
> 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.
Seems reasonable. What if we move that note to come after "any parent directory"?
On 2 Jul 2021, at 20:21, Bagas Sanjaya wrote:
> So for example I have `something/foo` in ../.gitignore, but .gitignore > (in current directory `something`) has `foo`. Is .gitignore from > current directory or ../.gitignore takes effect?
In this case, both rules resolve to the same path, so I don't think it matters? But in practice I'd expect it to be `something/.gitignore`, since you can negate the pattern from the parent ignore file.
> Also s/toplevel/top level/
That showed up in the diff due to word wrapping. If no other changes are accepted, I'll file a followup after to get this fixed on it's own.