martin f krafft wrote: > Yes, rsync/cp are enforcing the mode/ownership/group membership/ACL > data from the source onto the destination, which I don't think they > should.
git-annex lets rsync/cp preserve as much of the file metadata is they can, which is generally considered a good thing, and then adjusts the permissions per core.SharedRepository. I am still not at all clear what you think the bug is here. > which is all good and well, but then, the temporary file is renamed > to .git/annex/objects/Xp/JJ/SHA… in this case. git annex creates > those hash directories (which is not shown in the debug output), > using wrong permissions, before it moves the file to its final > destination (also not shown). Define "wrong permissions"? AFAIK, git-annex has good reasons to use the permissions it uses for objects directories. -- see shy jo
signature.asc
Description: Digital signature
