From eae89f73bb5cdbafe7ba405afbb7d85b4cb53a2b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 27 Sep 2022 14:31:06 -0400 Subject: [PATCH] comment --- ..._e262ec0e438557b8d70a6adc50545ac1._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/bugs/infinite_hang_on_git_status_with_v10___38___nfs/comment_2_e262ec0e438557b8d70a6adc50545ac1._comment diff --git a/doc/bugs/infinite_hang_on_git_status_with_v10___38___nfs/comment_2_e262ec0e438557b8d70a6adc50545ac1._comment b/doc/bugs/infinite_hang_on_git_status_with_v10___38___nfs/comment_2_e262ec0e438557b8d70a6adc50545ac1._comment new file mode 100644 index 0000000000..b200189dbc --- /dev/null +++ b/doc/bugs/infinite_hang_on_git_status_with_v10___38___nfs/comment_2_e262ec0e438557b8d70a6adc50545ac1._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2022-09-27T18:21:12Z" + content=""" +If filter-process is the problem, it does not make sense that repo v9 +v9 would not have the problem, because v9 enables filter-process. +If v9 is ok and only v10 has the problem then it must have something to +do with the locking changes in v10. + +Also, you can upgrade to v9/v10 and still disable git-annex filter-process, +by running this after the upgrade: + + git config --unset filter.annex.process + +(Note that git-annex had a bug that caused v9 to upgrade to v10 +without waiting the year it was supposed to. That bug is why your v9 repo +upgraded. That was fixed in today's git-annex release.) +"""]] -- 2.30.2