diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-10-19 13:36:24 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-10-19 13:36:24 -0400 |
| commit | f14c20b88212eceabbc85fe90c5a1964d29dd7fb (patch) | |
| tree | 2a1d7464f8d7fc6c572de5f7445688bbf3872828 | |
| parent | bc758e0386168cd0bc5b8fdf5e58d2ec1df8670a (diff) | |
response
| -rw-r--r-- | doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment b/doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment new file mode 100644 index 000000000..905184f95 --- /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. +"""]] |