2002-06-28 Marcus Brinkmann <marcus@g10code.de>

	* gpgme.texi (Multi Threading): Remove item about the need to
	synchronize anything against gpgme_wait (except gpgme_wait
	itself).

diff --git a/doc/ChangeLog b/doc/ChangeLog
index aaace19c9d552824270533589633bba4db28f764..09bebd2ad3217d81e9b9da5d91db496fc096953a 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,9 @@
+2002-06-28  Marcus Brinkmann  <marcus@g10code.de>
+
+       * gpgme.texi (Multi Threading): Remove item about the need to
+       synchronize anything against gpgme_wait (except gpgme_wait
+       itself).
+
 2002-06-27  Marcus Brinkmann  <marcus@g10code.de>
 
        * gpgme.texi (Information About Keys): Fix documentation for IDX.

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index e3bbfe9134861759abd739811711355e18265d05..aee6805ef34381c4a296ce00a79d71a440deefdc 100644 (file)
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -523,17 +523,9 @@ threads want to deal with the same object, the caller has to make sure
 that operations on this object are fully synchronized.
 
 @item
-Only one thread is allowed to call @code{gpgme_wait} at a time.  If
+Only one thread at any time is allowed to call @code{gpgme_wait}.  If
 multiple threads call this function, the caller must make sure that
 all invocations are fully synchronized.
-
-@item
-Unfortunately, the last rule implies that all calls to one of the
-following functions have to be fully synchronized together with
-@code{gpgme_wait}, as they call @code{gpgme_wait} internally: All
-functions @code{gpgme_op_FOO} that have a corresponding
-@code{gpgme_op_FOO_start} function, @code{gpgme_op_keylist_next},
-@code{gpgme_op_trustlist_next}.
 @end itemize