From 113ccfcc32c76ef07444a974cf0973b89d6147d2 Mon Sep 17 00:00:00 2001 From: "arnaud@c1d1cc612a3921dc06a417301be08a3e125478c4" Date: Thu, 21 Jul 2022 08:23:04 +0000 Subject: [PATCH] Added a comment: Happens only when core.untrackedCache=true --- ...omment_2_4d5eb77736e8512affc25e7bdd5190f1._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/Incompatibility_with_git_2.37/comment_2_4d5eb77736e8512affc25e7bdd5190f1._comment diff --git a/doc/bugs/Incompatibility_with_git_2.37/comment_2_4d5eb77736e8512affc25e7bdd5190f1._comment b/doc/bugs/Incompatibility_with_git_2.37/comment_2_4d5eb77736e8512affc25e7bdd5190f1._comment new file mode 100644 index 0000000000..b03714d4a2 --- /dev/null +++ b/doc/bugs/Incompatibility_with_git_2.37/comment_2_4d5eb77736e8512affc25e7bdd5190f1._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="arnaud@c1d1cc612a3921dc06a417301be08a3e125478c4" + nickname="arnaud" + avatar="http://cdn.libravatar.org/avatar/c0defbf54541c499f6c0464588fc2ad0" + subject="Happens only when core.untrackedCache=true" + date="2022-07-21T08:23:04Z" + content=""" +I did a little testing with potential triggers in my ~/.gitconfig and traced it down to core.untrackedCache=true + +With core.untrackedCache=true and git 2.36, everything works as expected. With git 2.37, I get the bug. +"""]] -- 2.30.2