diff --git a/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest.mdwn b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest.mdwn
index f136b25b3e..4f2abacc0b 100644
--- a/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest.mdwn
+++ b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest.mdwn
@@ -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://"]]
diff --git a/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_3_83fd8643b988fdf689ef40b819b48299._comment b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_3_83fd8643b988fdf689ef40b819b48299._comment
new file mode 100644
index 0000000000..2f46e29626
--- /dev/null
+++ b/doc/bugs/gcrypt_remote__58___every_sync_uploads_huge_manifest/comment_3_83fd8643b988fdf689ef40b819b48299._comment
@@ -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.
+"""]]