From 033e4da5a78b89bf3272aeefe65db1053431a97a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 19 Oct 2015 13:36:24 -0400 Subject: [PATCH] response --- ..._24_2c9eda62766c9d5000346a092fe5d0d8._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment diff --git a/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment b/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment new file mode 100644 index 0000000000..905184f958 --- /dev/null +++ b/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 24""" + date="2015-10-19T17:32:16Z" + content=""" +@craig, all of git-annex's information about a special remote is stored in +the git-annex branch in git, so any clone of the git repository is +sufficient to back that up. You can run `git annex enableremote` +in an clone to enable an existing special remote. + +The only catch is that, if you have chosen to initremote a special remote +using a gpg key, with `encryption=shared keyid=whatever`, you'll of course +also need that gpg key to to use it. If you run `git annex info $myremote` +it will tell you amoung other things, any gpg keys that are used by that +remote. +"""]]