aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/ChangeLog4
-rw-r--r--doc/gpgme.texi2
2 files changed, 5 insertions, 1 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index fba19d06..c87e2491 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,7 @@
+2004-09-28 Marcus Brinkmann <[email protected]>
+
+ * gpgme.texi (Passphrase Callback): Fix last change.
+
2004-09-27 Marcus Brinkmann <[email protected]>
* gpgme.texi (Passphrase Callback): Document
diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index 04a828a5..f63df520 100644
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -2069,7 +2069,7 @@ passphrase. It is better if the engine retrieves the passphrase from
a trusted agent (a daemon process), rather than having each user to
implement their own passphrase query. Some engines do not even
support an external passphrase callback at all, in this case the error
-code @code{GPG_ERR_NOT_SUPPORTED) is returned.
+code @code{GPG_ERR_NOT_SUPPORTED} is returned.
The user can disable the use of a passphrase callback function by
calling @code{gpgme_set_passphrase_cb} with @var{passfunc} being