Patch for gpgme.texi bug
Bernhard Herzog <[email protected]>
| Newsgroups | gmane.comp.encryption.gpg.gpa.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, I just tried to compile a current gpgme from CVS and it failed when building the docs. gpgme.texi has a wrong closing brace. See patch. Bernhard -- Intevation GmbH http://intevation.de/ Skencil http://sketch.sourceforge.net/ Thuban http://thuban.intevation.org/ _______________________________________________ Gpa-dev mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gpa-dev
gpgme-texi.diff
(text/x-diff, 1.1 KB)
Index: doc/gpgme.texi
===================================================================
RCS file: /cvs/gnupg/gpgme/doc/gpgme.texi,v
retrieving revision 1.130
diff -c -r1.130 gpgme.texi
*** doc/gpgme.texi 27 Sep 2004 20:24:48 -0000 1.130
--- doc/gpgme.texi 28 Sep 2004 11:11:28 -0000
***************
*** 2069,2075 ****
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.
The user can disable the use of a passphrase callback function by
calling @code{gpgme_set_passphrase_cb} with @var{passfunc} being
--- 2069,2075 ----
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.
The user can disable the use of a passphrase callback function by
calling @code{gpgme_set_passphrase_cb} with @var{passfunc} being