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

Added a comment: git-remote-gcrypt recommends rsync:// or sftp:// transports

Browse source
This commit is contained in:
git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00 2017-04-05 16:16:25 +00:00 committed by admin
parent eab6146e53
commit f6b1a2a027
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_2_02ae97849e2d9fc6d3d996500f264455._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00"
nickname="git-annex"
avatar="http://cdn.libravatar.org/avatar/198790d74209efe4896fd4cfc37ec2a6"
subject="git-remote-gcrypt recommends rsync:// or sftp:// transports"
date="2017-04-05T16:16:25Z"
content="""
spwhitton says on <https://github.com/spwhitton/git-remote-gcrypt>:
> \"Using an arbitrary <giturl> requires uploading the entire repository history with
> each push. If your repository history is large or you are pushing over a slow link, consider using
> either the rsync:// or sftp:// transports, which perform incremental pushes\"
So it's a known performance. Would be great if rsync:// could be used when combining git-annex with
git-remote-gcrypt?
"""]]