diff options
author | 2016-09-21 16:46:45 -0400 | |
---|---|---|
committer | 2016-09-21 16:46:45 -0400 | |
commit | 8e171441122b3bc7af2f3fe230f78c93f9936029 (patch) | |
tree | 16c47c13c2fb6de85984da55974f527ae2a5325d | |
parent | 7b46dce147500b40d597f9bdf8cc835596e2a5be (diff) |
comment
-rw-r--r-- | doc/forum/git_annex_file_content_replaced_with_symlink_content/comment_3_cc703ef5015527425572002295568923._comment | 13 |
1 files changed, 13 insertions, 0 deletions
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 000000000..43f5107ce --- /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. +"""]] |