summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar CandyAngel <CandyAngel@web>2016-05-10 17:44:38 +0000
committerGravatar admin <admin@branchable.com>2016-05-10 17:44:38 +0000
commit53286ac9268d7cb876672754b3b435da3ede4511 (patch)
tree0b892ba01ed29756e86d6487a431051d547d7445
parent99c66e4b7560271bafb27c7e91ca6845c33989b7 (diff)
Added a comment
-rw-r--r--doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_2_de77cc2bee45706c4bbe407d8846778e._comment13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_2_de77cc2bee45706c4bbe407d8846778e._comment b/doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_2_de77cc2bee45706c4bbe407d8846778e._comment
new file mode 100644
index 000000000..1d84df882
--- /dev/null
+++ b/doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_2_de77cc2bee45706c4bbe407d8846778e._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="CandyAngel"
+ subject="comment 2"
+ date="2016-05-10T17:44:38Z"
+ content="""
+It protects against adding in corrupted files without noticing.
+
+If I move the symlink as a real file, the receiving git-annex will rehash it and, if it is corrupted, effectively change the symlink to a corrupt file with no way to tell this has occured.
+
+This method leaves the transplanted symlink broken (and may be fixed by a reinject of a good copy of the file from another drive) and the corrupt content would be left behind by the reinject. This makes it very obvious something has happened.
+
+Thank you for making these changes to support my use case. I really hope it doesn't break anyone else's!
+"""]]