summaryrefslogtreecommitdiff
path: root/doc/special_remotes
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-08-15 12:02:40 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-08-15 12:02:40 -0400
commit6ae12e6340305db71dda3cced02e31076bdb1b33 (patch)
treec6e6bb1efe9d20a37ddef599e6fc3d1a567a9e22 /doc/special_remotes
parent4a0d79af6fdd23865b574565296fe726d4f60543 (diff)
clarify config option name
Diffstat (limited to 'doc/special_remotes')
-rw-r--r--doc/special_remotes/gcrypt.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/special_remotes/gcrypt.mdwn b/doc/special_remotes/gcrypt.mdwn
index c9a22b01a..d5f3f7b5b 100644
--- a/doc/special_remotes/gcrypt.mdwn
+++ b/doc/special_remotes/gcrypt.mdwn
@@ -46,7 +46,7 @@ force it to re-push everything again, so that the encrypted repository can
be decrypted by the added keys. Probably this can be done by setting
`GCRYPT_FULL_REPACK` and doing a forced push of branches.
-Recent versions of git-annex configure gcrypt-publish-participants when
+Recent versions of git-annex configure `remote.<name>`gcrypt-publish-participants` when
setting up a gcrypt repository. This is done to avoid unncessary gpg
passphrase prompts, but it does publish the gpg keyids that can decrypt the
repository. Unset it if you need to obscure that.