From 591e87f1f27c89f018547ddddbdafcb3c416e688 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 22 Jul 2022 12:24:42 -0400 Subject: [PATCH] reproduced --- .../comment_3_889ece8b2168b20019253ab6dd5b0e48._comment | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/bugs/Incompatibility_with_git_2.37/comment_3_889ece8b2168b20019253ab6dd5b0e48._comment b/doc/bugs/Incompatibility_with_git_2.37/comment_3_889ece8b2168b20019253ab6dd5b0e48._comment index a0c823267d..4bd9542003 100644 --- a/doc/bugs/Incompatibility_with_git_2.37/comment_3_889ece8b2168b20019253ab6dd5b0e48._comment +++ b/doc/bugs/Incompatibility_with_git_2.37/comment_3_889ece8b2168b20019253ab6dd5b0e48._comment @@ -12,6 +12,5 @@ Probably `git update-index`, since that's what looks at the config. waits for it to exit. So I don't understand what would have the index still locked. -I wonder if this is related to some other config also being set, such as -core.fsmonitor. +I've reproduced it, setting core.untrackedCache. """]]