2003-12-23 Moritz Schulte <mo@g10code.com>

	* gpgme.texi (Listing Keys): Minor clarification for
	gpgme_get_key.

diff --git a/doc/ChangeLog b/doc/ChangeLog
index 0064e2d23f563d2c1669f901264fbdbb420ef878..1589e4161f7b319cba8dd1834163a16345962fa7 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,8 @@
+2003-12-23  Moritz Schulte  <mo@g10code.com>
+
+       * gpgme.texi (Listing Keys): Minor clarification for
+       gpgme_get_key.
+
 2003-10-06  Marcus Brinkmann  <marcus@g10code.de>
 
        * gpgme.texi (Signal Handling): New section.

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index 480945485e1f2efcaab5495793c73912a8fa71fc..8c34f8975618f390ce260194df8e1ab9fa67b546 100644 (file)
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -2477,7 +2477,8 @@ following function can be used to retrieve a single key.
 The function @code{gpgme_get_key} gets the key with the fingerprint
 (or key ID) @var{fpr} from the crypto backend and return it in
 @var{r_key}.  If @var{secret} is true, get the secret key.  The
-currently active keylist mode is used to retrieve the key.
+currently active keylist mode is used to retrieve the key.  The key
+will have one reference for the user.
 
 If the key is not found in the keyring, @code{gpgme_get_key} returns
 the error code @code{GPG_ERR_NO_ERROR} and *@var{r_key} will be set to