[git] GPGME - branch, master, updated. gpgme-1.11.1-283-g91b26b0

by Ben McGinnes cvs at cvs.gnupg.org
Sun Sep 16 01:49:37 CEST 2018


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  91b26b0638d9f92f0e90aab1c3750c14d72db301 (commit)
      from  766ec0e4a36c120ed4ef5463b5fdf8e7ed3b4563 (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 91b26b0638d9f92f0e90aab1c3750c14d72db301
Author: Ben McGinnes <ben at adversary.org>
Date:   Sun Sep 16 09:47:05 2018 +1000

    docs: whitespace culled
    
    * lang/python/docs/gpgme-python-howto.org: Identified and fixed the
      headings which kept generating lines with trailing whitespace when
      exporting to Texinfo format and adjusted them to prevent that.

diff --git a/lang/python/docs/gpgme-python-howto.org b/lang/python/docs/gpgme-python-howto.org
index 68538e4..1f5ceb2 100644
--- a/lang/python/docs/gpgme-python-howto.org
+++ b/lang/python/docs/gpgme-python-howto.org
@@ -17,7 +17,7 @@
 
 | Version:        | 0.1.4                                    |
 | GPGME Version:  | 1.12.0-draft                             |
-| Author:         | Ben McGinnes <ben at gnupg.org>             |
+| Author:         | [[https://gnupg.org/people/index.html#sec-1-5][Ben McGinnes]] <ben at gnupg.org>             |
 | Author GPG Key: | DB4724E6FA4286C92B4E55C4321E4E2373590E5D |
 | Language:       | Australian English, British English      |
 | xml:lang:       | en-AU, en-GB, en                         |
@@ -401,7 +401,7 @@ Investigations into the extent or the limitations of this issue are
 ongoing.
 
 
-*** I don't like SWIG, Use CFFI instead
+*** CFFI is the Best™ and GPGME should use it instead of SWIG
     :PROPERTIES:
     :CUSTOM_ID: snafu-cffi
     :END:
@@ -438,6 +438,16 @@ running into trouble with "ifdefs" then you'll know what sort of
 things are lacking.  That doesn't even take into account the amount of
 work saved via SWIG's code generation techniques either.
 
+There's a greater likelihood of turning to Cython to add something to
+these bindings at this point than there is of turning to CFFI.  Except
+that there's little reason to do so when the C code in question either
+already exists or could be produced fairly quickly by the far more
+expedient means of asking either [[https://gnupg.org/people/index.html#sec-1-1][Werner]], [[https://gnupg.org/people/index.html#sec-1-3][Niibe]] or [[https://gnupg.org/people/index.html#sec-1-6][Andre]] to write
+whatever was missing.  Perhaps even [[https://gnupg.org/people/index.html#sec-1-4][Jussi]], but there shouldn't be any
+need for these bindings to interface directly with his work and for
+much the same reasons as we recommend people not call libgcrypt
+directly unless they know what they're doing.
+
 
 * Fundamentals
   :PROPERTIES:
@@ -2033,19 +2043,21 @@ converts them into crypt-hooks suitable for use with the Mutt and
 Neomutt mail clients.
 
 
-* Copyright and Licensing
+* Copyright, Draft Editions and Licensing
   :PROPERTIES:
   :CUSTOM_ID: copyright-and-license
   :END:
 
 
-** Copyright (C) The GnuPG Project, 2018
+** Copyright
    :PROPERTIES:
    :CUSTOM_ID: copyright
    :END:
 
 Copyright © The GnuPG Project, 2018.
 
+Copyright (C) The GnuPG Project, 2018.
+
 
 ** Draft Editions of this HOWTO
    :PROPERTIES:

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

Summary of changes:
 lang/python/docs/gpgme-python-howto.org | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)


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




More information about the Gnupg-commits mailing list