1 From: Werner Koch <wk@gnupg.org>
2 Date: Fri, 7 Apr 2017 10:26:55 +0200
3 Subject: doc: Explain the '>' in a key listing.
7 Signed-off-by: Werner Koch <wk@gnupg.org>
8 (cherry picked from commit 9c9fde1495be4accf4526a2626110876fd9d788d)
10 doc/gpg.texi | 11 +++++++----
11 1 file changed, 7 insertions(+), 4 deletions(-)
13 diff --git a/doc/gpg.texi b/doc/gpg.texi
14 index d658737..c591049 100644
17 @@ -301,10 +301,13 @@ and other programs.
19 @opindex list-secret-keys
20 List the specified secret keys. If no keys are specified, then all
21 -known secret keys are listed. A @code{#} after the letters @code{sec}
22 -means that the secret key is not usable (for example, if it was
23 -exported using @option{--export-secret-subkeys}). See also
24 -@option{--list-keys}.
25 +known secret keys are listed. A @code{#} after the intial tags
26 +@code{sec} or @code{ssb} means that the secret key or subkey is
27 +currently not usable. We also say that this key has been taken
28 +offline (for example, a primary key can be taken offline by exported
29 +the key using the command @option{--export-secret-subkeys}). A
30 +@code{>} after these tags indicate that the key is stored on a
31 +smartcard. See also @option{--list-keys}.
33 @item --list-signatures
34 @opindex list-signatures