aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Sokolovsky <paul.sokolovsky@linaro.org>2014-03-22 18:48:02 +0200
committerPaul Sokolovsky <paul.sokolovsky@linaro.org>2014-03-22 18:48:02 +0200
commit30deb3e664b2075c3b1c009e767b06149bc33666 (patch)
tree1be515ac262b5db0eee74540615052cd3265339b
parentcb7795ffecdc9225b88e74d0da65559b4786e924 (diff)
downloadgit-gpgcrypt-30deb3e664b2075c3b1c009e767b06149bc33666.tar.gz
Add explicit ref to man gpg for specifying recipients.
Change-Id: I0f0f6fb4d7bc886ed914d8bf5f5e2f3e5ae64b0f
-rw-r--r--README7
1 files changed, 4 insertions, 3 deletions
diff --git a/README b/README
index 9dc3a25..cf0b9a2 100644
--- a/README
+++ b/README
@@ -31,9 +31,10 @@ New repository
1. git init
2. Create ".recipients" file listing key names of persons who may access
encrypted files in the repository. These may be either key IDs or
-substrings of user IDs (e.g., emails). Note that corresponding keys must
-be already present in your keyring (TODO: add convenience command to import
-keys from keyserver).
+substrings of user IDs (e.g., emails). See "How to specify a user ID" in
+man gpg for more details. Note that corresponding keys must be already
+present in your keyring (TODO: add convenience command to import keys from
+keyserver).
3. git gpgcrypt init
4. Review .gitattributes file for file encryption settings (it's not required
to encrypt all files; in particular, default .gitattributes makes README and