summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-05-10 14:07:36 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-05-10 14:07:36 -0400
commit13f088073ed72b68ac5a5e5bab737f9ab63a7aa5 (patch)
tree6d09972ed1783417c3560c2bab5eb3849fa47678
parent72c53a3c6fc57bdd89bd4675d4c79ae27034f68c (diff)
parenta03c2109930f060ec48ed65d5d2dffef3dcb510d (diff)
Merge branch 'master' of ssh://git-annex.branchable.com
-rw-r--r--doc/forum/Making_a_git-annexy_symlink___34__known__34____63__/comment_2_de77cc2bee45706c4bbe407d8846778e._comment13
-rw-r--r--doc/forum/Wrong_symlink_target_on_usb_drive/comment_4_f6ee6bfd5d82f0925f0e174b4c75e592._comment27
2 files changed, 40 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!
+"""]]
diff --git a/doc/forum/Wrong_symlink_target_on_usb_drive/comment_4_f6ee6bfd5d82f0925f0e174b4c75e592._comment b/doc/forum/Wrong_symlink_target_on_usb_drive/comment_4_f6ee6bfd5d82f0925f0e174b4c75e592._comment
new file mode 100644
index 000000000..b80d95062
--- /dev/null
+++ b/doc/forum/Wrong_symlink_target_on_usb_drive/comment_4_f6ee6bfd5d82f0925f0e174b4c75e592._comment
@@ -0,0 +1,27 @@
+[[!comment format=mdwn
+ username="pixunil"
+ subject="git config"
+ date="2016-05-10T17:59:10Z"
+ content="""
+```
+[core]
+ repositoryformatversion = 0
+ filemode = false
+ bare = false
+ logallrefupdates = true
+ symlinks = true
+[annex]
+ uuid = ebd16ddb-548c-4078-b35e-087132523924
+ crippledfilesystem = true
+ version = 6
+[filter \"annex\"]
+ smudge = git-annex smudge %f
+ clean = git-annex smudge --clean %f
+# remote and user omitted
+```
+
+Gotcha! `core.symlinks` is `true`!
+I set it to `false` and running `unlock` works fine, but after `lock` the file contents gets replaced with the two digits directories (not the three digits directories which are the place where the object is saved). Also, I can't unlock the file afterwards anymore.
+
+However, I would be fine if symlinks work fine on other file system (as mentioned, would be great for saving space and have the access to the files) or other method.
+"""]]