From 162c8cdec0d5839e454f1e635848d606e9656043 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 22 Jul 2022 11:59:15 -0400 Subject: [PATCH] comment --- ..._3_889ece8b2168b20019253ab6dd5b0e48._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/Incompatibility_with_git_2.37/comment_3_889ece8b2168b20019253ab6dd5b0e48._comment 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 new file mode 100644 index 0000000000..a0c823267d --- /dev/null +++ b/doc/bugs/Incompatibility_with_git_2.37/comment_3_889ece8b2168b20019253ab6dd5b0e48._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2022-07-22T15:46:46Z" + content=""" +`git write-tree` has always locked the index, so it seems something else +has changed to also lock the index when core.untrackedCache is set, that +did not before. + +Probably `git update-index`, since that's what looks at the config. +`git-annex init` does run that, before `git write-tree`, but it +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. +"""]]