Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2016-05-10 14:07:36 -04:00
commit 5ae4c1987f
Failed to extract signature
2 changed files with 40 additions and 0 deletions

View file

@ -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!
"""]]

View file

@ -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.
"""]]