[git] GPGME - branch, master, updated. gpgme-1.9.0-65-g0ee7f4f

[by Marcus Brinkmann]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GnuPG Made Easy".

The branch, master has been updated
       via  0ee7f4f178284dae153a59be710bc994820369e5 (commit)
      from  3244d4daff892d5d3c39e78f4eb0934379beda2c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 0ee7f4f178284dae153a59be710bc994820369e5
Author: Marcus Brinkmann <marcus.brinkmann at ruhr-uni-bochum.de>
Date:   Wed Aug 16 15:39:17 2017 +0200

    doc: Clarify import keys operation further.
    
    * doc/gpgme.texi (gpgme_op_import_keys): Further clarifications.
    
    Signed-off-by: Marcus Brinkmann <mb at g10code.com>
    GnuPG-bug-id: 3215

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index 78859cd..5ea16b9 100644
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -4458,9 +4458,12 @@ The function @code{gpgme_op_import_keys} adds the keys described by
 the @code{NULL} terminated array @var{keys} to the key ring of the
 crypto engine used by @var{ctx}.  It is used to actually import and
 make keys permanent which have been retrieved from an external source
-(i.e. using @code{GPGME_KEYLIST_MODE_EXTERN}).  @footnote{Thus it is a
+(i.e. using @code{GPGME_KEYLIST_MODE_EXTERN}) earlier.  The external
+keylisting must have been made with the same context configuration (in
+particular the same home directory).  @footnote{Thus it is a
 replacement for the usual workaround of exporting and then importing a
-key to make an X.509 key permanent.}
+key to make an X.509 key permanent.}  Note that for OpenPGP this may
+require another access to the keyserver over the network.
 
 Only keys of the currently selected protocol of @var{ctx} are
 considered for import.  Other keys specified by the @var{keys} are
@@ -4470,6 +4473,9 @@ the same method, i.e. the used key listing mode must be identical.
 After the operation completed successfully, the result can be
 retrieved with @code{gpgme_op_import_result}.
 
+To move keys from one home directory to another, export and import the
+keydata using @code{gpgme_op_export} and @code{gpgme_op_import}.
+
 The function returns the error code @code{GPG_ERR_NO_ERROR} if the
 import was completed successfully, @code{GPG_ERR_INV_VALUE} if
 @var{ctx} is not a valid pointer, @code{GPG_ERR_CONFLICT} if the key

-----------------------------------------------------------------------

Summary of changes:
 doc/gpgme.texi | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
GnuPG Made Easy
http://git.gnupg.org