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

followup

Browse source
This commit is contained in:
Joey Hess 2020-09-08 12:17:08 -04:00
parent 62372ee052
commit 54404370e5
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/bugs/fails_to_preserve_mode_bits___40__executable_files_becomes_non-executable.mdwn
View file

@ -47,3 +47,4 @@ I have my private binaries in ~/annex/bin and this has worked well for many year
I've used git-annex since summer 2012, it's great :-)
> [[notabug|done]] --[[Joey]]

19
doc/bugs/fails_to_preserve_mode_bits___40__executable_files_becomes_non-executable/comment_1_7e4599871d40c07cc30e0b9487288e3a._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-09-08T16:11:01Z"
content="""
Appears that you already had an empty file in the repository. Since
git-annex deduplicates content, it used the content of that empty file
for the new file you added. The empty file was created in 2015 is a
giveaway.
Do note that many git-annex special remotes cannot preserve modes or
other metadata of files anyway, so after moving a file to a remote and
getting it back, the mode can be reset to default.
The mode is not version controlled when you check a symlink into git,
because symlinks do not have
modes.. If you want to preserve execute bits, the only way to guarantee it
will happen is to add the file unlocked. Then git tracks the execute bit.
"""]]