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

Added a comment

Browse source
This commit is contained in:
git-annex.branchable.com@79d6855760f61f7fbe0a401b45d8c791ef49b500 2020-08-02 23:41:33 +00:00 • committed by admin
parent 5a5e13e972
commit 465842f3f6
1 changed files with 9 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_8_3122eeb1f540bdde320beb2eda196221._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="git-annex.branchable.com@79d6855760f61f7fbe0a401b45d8c791ef49b500"
nickname="git-annex.branchable.com"
avatar="http://cdn.libravatar.org/avatar/4bf61f9feda20e8b4fc09d52ee48af39"
subject="comment 8"
date="2020-08-02T23:41:32Z"
content="""
Is it possible to convert an existing `gcrypt::ssh://host/path` gcrypt special remote to one on top of rsync transport protocol to work around these performance issues? The existing remote is obviously quite large, and re-uploading the content would take a very long time.
"""]]