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 2017-04-05 14:47:49 -04:00
parent 8c722069ea
commit ee8bbf33bb
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest.mdwn
View file

@ -26,3 +26,5 @@ is running. The upload of the actual changeset starts after this, the processes
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
git-annex is great and revolutionized my file organization and backup structure (if they were even existing before)
[[!meta tite="gcrypt special remotes should support rsync:// and perhaps also sftp://"]]

20
doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_3_83fd8643b988fdf689ef40b819b48299._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2017-04-05T18:35:30Z"
content="""
It should be possible for git-annex to support rsync:// for gcrypt special
remotes; that would just need to reuse the rsync special remote for the
git-annex objects. Retitling this bug report appropriately.
In the meantime, it should work to set up a gcrypt git remote (not a
git-annex special remote) using rsync:// or sftp:// and then use a
git-annex rsync special remote on the same server to store the annex
objects.
But that doesn't help with large pushes to gcrypt remotes
when git hosting providers are being used, which is a main
use case for using gcrypt (though generally not the gcrypt special remote).
The lack of incrementals there seems like something worth finding a way to
fix in gcrypt.
"""]]