mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

response

Browse source
This commit is contained in:
Joey Hess 2015-10-19 13:36:24 -04:00
parent 9d0f5e5c02
commit 033e4da5a7
Failed to extract signature
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/special_remotes/comment_24_2c9eda62766c9d5000346a092fe5d0d8._comment Normal file
View file

@ -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.
"""]]