2003-04-25 Marcus Brinkmann <marcus@g10code.de>

* gpgme.texi (Importing Keys): Remove note about gpgme_get_op_info.
	(Detailed Results): Remove note about import.
This commit is contained in:
Marcus Brinkmann 2003-04-25 16:11:25 +00:00
parent 8cfb3cdd07
commit d99f1faa17
2 changed files with 4 additions and 5 deletions

View File

@ -1,5 +1,8 @@
2003-04-25 Marcus Brinkmann <marcus@g10code.de>
* gpgme.texi (Importing Keys): Remove note about gpgme_get_op_info.
(Detailed Results): Remove note about import.
* gpgme.texi (Importing Keys): Add documentation for
GpgmeImportStatus, GpgmeImportResult and gpgme_op_import_result.

View File

@ -2263,9 +2263,6 @@ The function @code{gpgme_op_import} adds the keys in the data buffer
The format of @var{keydata} can be @var{ASCII} armored, for example,
but the details are specific to the crypto engine.
More information about the import is available with
@code{gpgme_get_op_info}. @xref{Detailed Results}.
The function returns @code{GPGME_No_Error} if the import was completed
successfully, @code{GPGME_Invalid_Value} if @var{keydata} if @var{ctx}
or @var{keydata} is not a valid pointer, and @code{GPGME_No_Data} if
@ -3171,8 +3168,7 @@ Here is a sample of the information that might be returned:
@end example
Currently, the only operations that return additional information are
encrypt, sign and import. @xref{Encrypt}, @xref{Sign},
@xref{Importing Keys}.
encrypt, sign. @xref{Encrypt}, @xref{Sign}.
The function returns a string or @code{NULL} if no such data is
available.