3 subject="""comment 2"""
4 date="2018-10-18T19:45:15Z"
6 When two files have the same content, annex.thin will only make one of them
7 be a hard link to the annex object. The other file will have its own
8 redundant copy of the content. This is the only way to prevent an edit to
9 one file immediatly changing the other file, which would be very surprising
12 When the file in git has the executable bit set, annex.thin is not honored
13 for that file either. That's a lot simpler than juggling permissions
16 Does that explain everything you're seeing, or is there still a bug buried
17 in that transcript? I have not had time to read the whole thing.