diff options
author | 2017-04-05 11:47:08 -0400 | |
---|---|---|
committer | 2017-04-05 11:47:08 -0400 | |
commit | 52e15e4e9dc2f2110d484cc2bdfb03ee3c7d88fc (patch) | |
tree | 33262fb309356e06457f5958d9682e8c29477f3e | |
parent | 820366f9c153f1f6c8307459552544ee02b3b396 (diff) |
comment
-rw-r--r-- | doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_1_45982ced836d2e0f41a5ddd7edd59936._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_1_45982ced836d2e0f41a5ddd7edd59936._comment b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_1_45982ced836d2e0f41a5ddd7edd59936._comment new file mode 100644 index 000000000..065ca658b --- /dev/null +++ b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_1_45982ced836d2e0f41a5ddd7edd59936._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-04-05T15:44:47Z" + content=""" +I don't think this is a bug in git-annex. That is the behavior of +`git-remote-gcrypt`. Could you please file a bug on that program instead? + +(I've also wondered about this; it could be that it's re-uploading the +manifest every time for good security reasons, or it could be that a better +file structure would allow more incremental uploads. It certianly +seems like it could avoid re-uploading when nothing has changed!) +"""]] |