From: Junio C Hamano <gitster@pobox.com>
To: "Rahn, René" <Rene.Rahn@pfizer.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git-add ignores exclude markers for ignored files
Date: Tue, 04 Nov 2025 14:11:20 -0800 [thread overview]
Message-ID: <xmqqtsz9o3cn.fsf@gitster.g> (raw)
In-Reply-To: <MN0PR01MB761143093D1A4D226E8883A380C4A@MN0PR01MB7611.prod.exchangelabs.com> ("Rahn, René"'s message of "Tue, 4 Nov 2025 15:59:41 +0000")
"Rahn, René" <Rene.Rahn@pfizer.com> writes:
> Steps to reproduce:
>
> mkdir git-add-test
> cd git-add-test
> git init
> touch .gitignore
> echo “ignored.txt” >>.gitignore
> touch ignored.txt
> git add --“:(exclude)ignored.txt”
>
> Expected behavior:
>
> The git add command recognizes that the file ignored.txt is
> already excluded despite of it being ignored by some gitignore and
> thus does not check if it is ignored or not. It simply will not be
> added. Note forcing git-add will do the trick, but this could
> also have side effects for some files that are ignored but not
> present in the list of excluded files. Hence, this can’t be the
> right solution.
It is not quite clear what you want to see. The command would not
add ignored.text even if you give ":(exclude)ignored.txt" from the
command line, would it?
This may be an ancient regression when e1b8c7bd (dir: remove struct
path_simplify, 2017-01-04) was rewritten exclude_matches_pathspec()
function, which was written in 29209cbe (dir: fix COLLECT_IGNORED on
excluded prefixes, 2010-03-11), back in the days before ":(exclude)"
and other pathspec magic was even invented.
Perhaps try this patch?
I have no idea what the ramifications of the change is, though.
There may be unintended fallouts in some distant corner, even though
it does not seem to break any existing tests.
----- >8 -----
Subject: dir.c: do not be fooled by :(exclude) pathspec elements
When exclude_matches_pathspec() tries to determine if an otherwise
excluded item matches the pathspec given, it goes through each
pathspec element and declares a hit, without checking if the element
is a negative ":(exclude)" element. Fix it be applying the usual "a
path matches if it matches any one of positive pathspec element, and
if it matches none of negative pathspec elements" rule in the
function.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
diff --git a/dir.c b/dir.c
index 5b2181e589..5b1258a09d 100644
--- a/dir.c
+++ b/dir.c
@@ -2219,6 +2219,8 @@ static int exclude_matches_pathspec(const char *path, int pathlen,
const struct pathspec *pathspec)
{
int i;
+ int matches_exclude_magic = 0;
+ int matches_pathspec_elem = 0;
if (!pathspec || !pathspec->nr)
return 0;
@@ -2235,15 +2237,23 @@ static int exclude_matches_pathspec(const char *path, int pathlen,
for (i = 0; i < pathspec->nr; i++) {
const struct pathspec_item *item = &pathspec->items[i];
int len = item->nowildcard_len;
+ int *matches;
+
+ if (item->magic & PATHSPEC_EXCLUDE)
+ matches = &matches_exclude_magic;
+ else
+ matches = &matches_pathspec_elem;
if (len == pathlen &&
!ps_strncmp(item, item->match, path, pathlen))
- return 1;
+ *matches = 1;
if (len > pathlen &&
item->match[pathlen] == '/' &&
!ps_strncmp(item, item->match, path, pathlen))
- return 1;
+ *matches = 1;
}
+ if (matches_pathspec_elem && !matches_exclude_magic)
+ return 1;
return 0;
}
diff --git a/t/t2204-add-ignored.sh b/t/t2204-add-ignored.sh
index 31eb233df5..aa55b219ab 100755
--- a/t/t2204-add-ignored.sh
+++ b/t/t2204-add-ignored.sh
@@ -89,4 +89,21 @@ do
'
done
+test_expect_success "exclude magic would not interfere with .gitignore" '
+ test_write_lines dir file sub ign err out "*.o" >.gitignore &&
+ >foo.o &&
+ >foo.c &&
+ test_must_fail git add foo.o 2>err &&
+ test_grep "are ignored by one" err &&
+ test_grep "hint: Use -f" err &&
+
+ git add ":(exclude)foo.o" &&
+ git ls-files >actual &&
+ cat >expect <<-\EOF &&
+ .gitignore
+ foo.c
+ EOF
+ test_cmp expect actual
+'
+
test_done
next prev parent reply other threads:[~2025-11-04 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 15:59 git-add ignores exclude markers for ignored files Rahn, René
2025-11-04 22:11 ` Junio C Hamano [this message]
2025-11-05 0:54 ` Junio C Hamano
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=xmqqtsz9o3cn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Rene.Rahn@pfizer.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.
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 NNTP newsgroup(s).