From 081735b9679cfe6e70ef89743c6ba85a4f8a3707 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 13 May 2025 10:57:30 -0400 Subject: [PATCH] response --- ...ent_4_b6ac0341afd1c15eed0af4161db9c021._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/news/version_10.20250416/comment_4_b6ac0341afd1c15eed0af4161db9c021._comment diff --git a/doc/news/version_10.20250416/comment_4_b6ac0341afd1c15eed0af4161db9c021._comment b/doc/news/version_10.20250416/comment_4_b6ac0341afd1c15eed0af4161db9c021._comment new file mode 100644 index 0000000000..83d87f4084 --- /dev/null +++ b/doc/news/version_10.20250416/comment_4_b6ac0341afd1c15eed0af4161db9c021._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2025-05-13T14:55:52Z" + content=""" +First of all, a news item for a release is not the appropriate place to +discuss something like this. Use the [[forum]] in the furture. + +This looks like a `.git/annex/index` that references a git object that for +some reason didn't get written to disk. A common way this can happen is a +disk getting unmounted or system shutdown at a point in time that causes a +recently written git object to get lost. Deleting `.git/annex/index` will +solve this problem. +"""]]