From: Marcus Brinkmann Date: Tue, 28 Sep 2004 11:42:06 +0000 (+0000) Subject: 2004-09-28 Marcus Brinkmann X-Git-Tag: gpgme-1.2.0@1385~396 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=a48d63b825467135885d996656ae7446c3715799;p=gpgme.git 2004-09-28 Marcus Brinkmann * gpgme.texi (Passphrase Callback): Fix last change. --- diff --git a/trunk/doc/ChangeLog b/trunk/doc/ChangeLog index fba19d0..c87e249 100644 --- a/trunk/doc/ChangeLog +++ b/trunk/doc/ChangeLog @@ -1,3 +1,7 @@ +2004-09-28 Marcus Brinkmann + + * gpgme.texi (Passphrase Callback): Fix last change. + 2004-09-27 Marcus Brinkmann * gpgme.texi (Passphrase Callback): Document diff --git a/trunk/doc/gpgme.texi b/trunk/doc/gpgme.texi index 04a828a..f63df52 100644 --- a/trunk/doc/gpgme.texi +++ b/trunk/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