response
This commit is contained in:
parent
bd72dfeaa1
commit
5ddfd4f524
1 changed files with 18 additions and 0 deletions
|
@ -0,0 +1,18 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 2"""
|
||||||
|
date="2018-10-18T19:45:15Z"
|
||||||
|
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.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
Does that explain everything you're seeing, or is there still a bug buried
|
||||||
|
in that transcript? I have not had time to read the whole thing.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue