From: Junio C Hamano <gitster@pobox•com>
To: Dan Drake <dan@dandrake•org>
Cc: "git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: gitignore documentation for info/exclude files and patterns with relative directories
Date: Fri, 27 Mar 2026 09:18:45 -0700 [thread overview]
Message-ID: <xmqqwlyxkzyy.fsf@gitster.g> (raw)
In-Reply-To: <Qdk5yVH_yWgKl_bjCjdasusfe3PuzHCZ2rKgKIn2Xx5rcw46jmQDfA6K2vkv3V3XLSy4aqwyUlfVEmF5VlIv3EVEOlZLEnf-paw11tyhZKE=@dandrake.org> (Dan Drake's message of "Fri, 27 Mar 2026 11:20:42 +0000")
Dan Drake <dan@dandrake•org> writes:
> The documentation should mention this behavior for info/exclude, as well as
> the core.excludesFile.
Yup, my mistake more than 20-year-old that nobody complained so far
;-)
Yes, these exclude pattern sources that are outside the working tree
behave as if they are specified at the root level of the working
tree.
Patches welcome. Thanks.
next prev parent reply other threads:[~2026-03-27 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 11:20 gitignore documentation for info/exclude files and patterns with relative directories Dan Drake
2026-03-27 16:18 ` Junio C Hamano [this message]
2026-03-28 15:21 ` [PATCH] doc: gitignore: clarify pattern base for info/exclude and core.excludesFile Shreyansh Paliwal
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwlyxkzyy.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=dan@dandrake$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox