From f7ac2bc8687f559fe37a3b16c7fc2ee98e5e644a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 21 Sep 2016 16:46:45 -0400 Subject: [PATCH] comment --- ...ment_3_cc703ef5015527425572002295568923._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/git_annex_file_content_replaced_with_symlink_content/comment_3_cc703ef5015527425572002295568923._comment diff --git a/doc/forum/git_annex_file_content_replaced_with_symlink_content/comment_3_cc703ef5015527425572002295568923._comment b/doc/forum/git_annex_file_content_replaced_with_symlink_content/comment_3_cc703ef5015527425572002295568923._comment new file mode 100644 index 0000000000..43f5107ce0 --- /dev/null +++ b/doc/forum/git_annex_file_content_replaced_with_symlink_content/comment_3_cc703ef5015527425572002295568923._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-09-21T20:44:26Z" + content=""" +Gold star for @jimparis! + +Another way to get out of this situation would be to edit the files, +and remove the initial lines so it contains a single line that is +the link target of the symlink (the bit with .git/annex/objects in it). + +Then, `git annex fsck` would be able to fix up the files. +"""]]