diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-09-14 14:49:48 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-09-14 14:49:48 -0400 |
| commit | 772f686a33e17ce104d0a9e5cc28a70e28250eb2 (patch) | |
| tree | 067ebe52d8b461ca27e56d5944ae1d391972006b /doc/git-annex-enableremote.mdwn | |
| parent | d8bc62fed9ae2e85235fde7a6cba5f522daf6014 (diff) | |
Special remotes configured with autoenable=true will be automatically enabled when git-annex init is run.
Diffstat (limited to 'doc/git-annex-enableremote.mdwn')
| -rw-r--r-- | doc/git-annex-enableremote.mdwn | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/doc/git-annex-enableremote.mdwn b/doc/git-annex-enableremote.mdwn index 79b224a04..3b543c969 100644 --- a/doc/git-annex-enableremote.mdwn +++ b/doc/git-annex-enableremote.mdwn @@ -19,14 +19,14 @@ special remote names. Some special remotes may need parameters to be specified every time they are enabled. For example, the directory special remote requires a directory= -parameter. - +parameter every time. + This command can also be used to modify the configuration of an existing -special remote, by specifying new values for parameters that were -originally set when using initremote. (However, some settings such as +special remote, by specifying new values for parameters that are +usually set when using initremote. (However, some settings such as the as the encryption scheme cannot be changed once a special remote has been created.) - + The GPG keys that an encrypted special remote is encrypted with can be changed using the keyid+= and keyid-= parameters. These respectively add and remove keys from the list. However, note that removing a key @@ -45,6 +45,12 @@ on files that have already been copied to the remote. Hence using keyid+= and keyid-= with such remotes should be used with care, and make little sense except in cases like the revoked key example above. +If you get tired of manually enabling a special remote in each new clone, +you can pass "autoenable=true". Then when [[git-annex-init]](1) is run in +a new clone, it will will attempt to enable the special remote. Of course, +this works best when the special remote does not need anything special +to be done to get it enabled. + # SEE ALSO [[git-annex]](1) |