diff options
Diffstat (limited to '')
| -rw-r--r-- | doc/ChangeLog | 6 | ||||
| -rw-r--r-- | doc/gpgme.texi | 10 |
2 files changed, 7 insertions, 9 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog index aaace19c..09bebd2a 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,9 @@ +2002-06-28 Marcus Brinkmann <[email protected]> + + * gpgme.texi (Multi Threading): Remove item about the need to + synchronize anything against gpgme_wait (except gpgme_wait + itself). + 2002-06-27 Marcus Brinkmann <[email protected]> * gpgme.texi (Information About Keys): Fix documentation for IDX. diff --git a/doc/gpgme.texi b/doc/gpgme.texi index e3bbfe91..aee6805e 100644 --- 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 |