mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
andrey_utkin@49e37627b3060c40292113d73d7ffbf317233e62 2018-10-18 20:18:01 +00:00 • committed by admin
parent 5ddfd4f524
commit 82040ae2aa
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/v6_hardlinking_is_not_stable_across_lock__47__unlock_or_cloning/comment_3_cbe7f29914091bc9de49dab8f4ed6003._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="andrey_utkin@49e37627b3060c40292113d73d7ffbf317233e62"
nickname="andrey_utkin"
avatar="http://cdn.libravatar.org/avatar/95bb7f4f7647cc24c1cf635b61578842"
subject="comment 3"
date="2018-10-18T20:18:01Z"
content="""
> When two files have the same content, annex.thin will only make one of them be a hard link to the annex object. The other file will have its own redundant copy of the content. This is the only way to prevent an edit to one file immediatly changing the other file, which would be very surprising behavior.
Ah, that explains my biggest confusion. Thanks!
> When the file in git has the executable bit set, annex.thin is not honored for that file either. That's a lot simpler than juggling permissions around.
Ok, I will take a note. But was it this way from the very beginning, or is this a later-added idea? From my observations, this is not true. I do have a large annex repo, I have done a global `chmod -R u=rwx,g=rx,o=rx *`, all my files have exec bit set and all of them are hardlinked (except for the files which are duplicates of other hardlinked files). I don't remember for sure, it might be that I've chmod-ed files in .git/annex/objects as well :)
"""]]