[Pkg-gnupg-commit] [gnupg2] 07/42: doc: clarify that --encrypt refers to public key encryption

[Daniel Kahn Gillmor]

This is an automated email from the git hooks/post-receive script.

dkg pushed a commit to branch upstream
in repository gnupg2.

commit 8a2917345ba88159bce6153b54706e701564f189
Author: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Date:   Fri Nov 17 10:17:08 2017 +0800

    doc: clarify that --encrypt refers to public key encryption
    
    --
    
    A simple read of gpg(1) is ambiguous about whether --encrypt could be
    for either symmetric or pubkey encryption.  Closer inference suggests
    that --encrypt is about pubkey encryption only.  Make that clearer on
    a first read.
    
    Signed-off-by: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
---
 doc/gpg.texi | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/doc/gpg.texi b/doc/gpg.texi
index bd45b04..35bb9a8 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -196,11 +196,13 @@ Make a detached signature.
 @item --encrypt
 @itemx -e
 @opindex encrypt
-Encrypt data. This command may be combined with @option{--sign} (to
-sign and encrypt a message), @option{--symmetric} (to encrypt a
-message that can decrypted using a secret key or a passphrase), or
- at option{--sign} and @option{--symmetric} together (for a signed
-message that can be decrypted using a secret key or a passphrase).
+Encrypt data to one or more public keys. This command may be combined
+with @option{--sign} (to sign and encrypt a message),
+ at option{--symmetric} (to encrypt a message that can decrypted using a
+secret key or a passphrase), or @option{--sign} and
+ at option{--symmetric} together (for a signed message that can be
+decrypted using a secret key or a passphrase).  @option{--recipient}
+and related options specify which public keys to use for encryption.
 
 @item --symmetric
 @itemx -c

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gnupg/gnupg2.git