From d8ad2d888994de08e1ee8c35c301531ce6a5ad2e Mon Sep 17 00:00:00 2001 From: tomdhunt Date: Sun, 9 Jan 2022 05:45:35 +0000 Subject: [PATCH] Added a comment --- ...comment_2_08245fd6716ee3ed5ac98fe95e7d5ca1._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/special_remotes/gcrypt/comment_2_08245fd6716ee3ed5ac98fe95e7d5ca1._comment diff --git a/doc/special_remotes/gcrypt/comment_2_08245fd6716ee3ed5ac98fe95e7d5ca1._comment b/doc/special_remotes/gcrypt/comment_2_08245fd6716ee3ed5ac98fe95e7d5ca1._comment new file mode 100644 index 0000000000..425f696e59 --- /dev/null +++ b/doc/special_remotes/gcrypt/comment_2_08245fd6716ee3ed5ac98fe95e7d5ca1._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="tomdhunt" + avatar="http://cdn.libravatar.org/avatar/02694633d0fb05bb89f025cf779218a3" + subject="comment 2" + date="2022-01-09T05:45:35Z" + content=""" +The gcrypt special remote is for use with the git-remote-gcrypt protocol for making encrypted git remotes. The rsync special remote can also encrypt the files it stores, but it's not related to git-remote-gcrypt; it just puts files in a plain directory tree using rsync. + +If you want to keep a repository remote (not a special remote) on your rsync.net host, and want it to be encrypted, then you can use git-remote-gcrypt and use this special remote so that the data is all together. If you're not using git-remote-gcrypt, then the rsync special remote is what you want. +"""]] -- 2.39.5