comment
authorJoey Hess <joeyh@joeyh.name>
Fri, 22 Jul 2022 15:59:15 +0000 (11:59 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 22 Jul 2022 15:59:15 +0000 (11:59 -0400)
doc/bugs/Incompatibility_with_git_2.37/comment_3_889ece8b2168b20019253ab6dd5b0e48._comment [new file with mode: 0644]

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 (file)
index 0000000..a0c8232
--- /dev/null
@@ -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.
+"""]]