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

response; update man page

Browse source
This commit is contained in:
Joey Hess 2017-05-09 14:02:48 -04:00
parent 05b1dee353
commit dccd7ba6d4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 28 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
doc/sync/comment_23_e5e7ec9fbafe5e0429161b977e483752._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 23"""
date="2017-05-09T17:52:11Z"
content="""
@mario, great question! (Not the best place for such a question, start a
thread on the forum next time..)
git-annex does use rsync when transferring files between ssh remotes.
Rsync normally goes over ssh, and it might be better to enable compression
at the ssh level. For example, I have "Compression yes" in `~/.ssh/config`
I think that the reason your annex-rsync-upload-options setting broke
it is that rsync needs --compress to be passed on to the other
rsync process (in the remote repository), and that is run via
git-annex-shell, which has a whitelist of options it will pass to rsync.
Passing arbitrary options to rsync could allow unwanted behavior
when git-annex-shell is being used as a security barrier. And --compress is
one of the options that both the rsync sender and receiver have to agree
on for the rsync protocol to work.
I have added a note to the man page about this limitation of what
the rsync-options settings can be used to do.
"""]]