[git] GPGME - branch, master, updated. gpgme-1.11.1-327-g033da18
by Ben McGinnes
cvs at cvs.gnupg.org
Thu Oct 4 18:42:42 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 033da18b88af69b7846de62af4aeea359d27ec20 (commit)
via a8d4aa6f763599bbd8ea36ef98b7b4931bf326dc (commit)
via 0b5930b276186afd1ca1dd91d82db7e60dd20606 (commit)
via 48258879720a4f423d0efa955da942d69f3c49d4 (commit)
from f3fc73738264d21baf0e9b49fdd5cb67faa11d31 (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 033da18b88af69b7846de62af4aeea359d27ec20
Author: Ben McGinnes <ben at adversary.org>
Date: Fri Oct 5 02:41:45 2018 +1000
docs: whitespace bug
* Same as before, but exported.
diff --git a/lang/python/doc/rst/short-history.rst b/lang/python/doc/rst/short-history.rst
index 0d839a5..8cf604f 100644
--- a/lang/python/doc/rst/short-history.rst
+++ b/lang/python/doc/rst/short-history.rst
@@ -19,10 +19,10 @@ Keeping the flame alive
-----------------------
A couple of years later the project was picked up by Igor Belyi and
-actively developed and maintained by him from 2004 to 2008. Igor\'s
-whereabouts at the time of this document\'s creation are unknown, but
-the current authors do hope he is well. We\'re assuming (or hoping) that
-life did what life does and made continuing untenable.
+actively developed and maintained by him from 2004 to 2008. Igor's
+whereabouts at the time of this document's creation are unknown, but the
+current authors do hope he is well. We're assuming (or hoping) that life
+did what life does and made continuing untenable.
Passing the torch
-----------------
@@ -110,7 +110,7 @@ this module or a sample of its content:
.. _pypi-gpgme-180:
-GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library
+GPG 1·8·0 - Python bindings for GPGME GnuPG cryptography library
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is the most recent version to reach PyPI and is the version of the
@@ -125,7 +125,7 @@ bindings included with that package.
.. _pypi-gpgme-90:
-PyME 0.9.0 - Python support for GPGME GnuPG cryptography library
+PyME 0·9·0 - Python support for GPGME GnuPG cryptography library
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is the last release of the PyME bindings maintained by Martin
@@ -135,7 +135,7 @@ Python 2 to Python 3 code was made in 2015.
Users of the more recent Python bindings will recognise numerous points
of similarity, but also significant differences. It is likely that the
-more recent official bindings will feel \"more pythonic.\"
+more recent official bindings will feel "more pythonic."
For those using Python 2, there is essentially no harm in using this
module, but it may lack a number of more recent features added to GPGME.
diff --git a/lang/python/doc/texinfo/short-history.texi b/lang/python/doc/texinfo/short-history.texi
index fd136b5..a982f02 100644
--- a/lang/python/doc/texinfo/short-history.texi
+++ b/lang/python/doc/texinfo/short-history.texi
@@ -40,8 +40,8 @@ Relics of the past
The Perils of PyPI
-* GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library: GPG 180 - Python bindings for GPGME GnuPG cryptography library.
-* PyME 0.9.0 - Python support for GPGME GnuPG cryptography library: PyME 090 - Python support for GPGME GnuPG cryptography library.
+* GPG 1·8·0 - Python bindings for GPGME GnuPG cryptography library::
+* PyME 0·9·0 - Python support for GPGME GnuPG cryptography library::
@end detailmenu
@end menu
@@ -172,12 +172,12 @@ pyme (0.9.0) - Python support for GPGME GnuPG cryptography library
@end enumerate
@menu
-* GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library: GPG 180 - Python bindings for GPGME GnuPG cryptography library.
-* PyME 0.9.0 - Python support for GPGME GnuPG cryptography library: PyME 090 - Python support for GPGME GnuPG cryptography library.
+* GPG 1·8·0 - Python bindings for GPGME GnuPG cryptography library::
+* PyME 0·9·0 - Python support for GPGME GnuPG cryptography library::
@end menu
- at node GPG 180 - Python bindings for GPGME GnuPG cryptography library
- at subsection GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library
+ at node GPG 1·8·0 - Python bindings for GPGME GnuPG cryptography library
+ at subsection GPG 1·8·0 - Python bindings for GPGME GnuPG cryptography library
This is the most recent version to reach PyPI and is the version
of the official Pyhon bindings which shipped with GPGME 1.8.0. If
@@ -189,8 +189,8 @@ As there have been a lot of changes since the release of GPGME
module and instead installing the current version of GPGME along
with the Python bindings included with that package.
- at node PyME 090 - Python support for GPGME GnuPG cryptography library
- at subsection PyME 0.9.0 - Python support for GPGME GnuPG cryptography library
+ at node PyME 0·9·0 - Python support for GPGME GnuPG cryptography library
+ at subsection PyME 0·9·0 - Python support for GPGME GnuPG cryptography library
This is the last release of the PyME bindings maintained by Martin
Albrecht and is only compatible with Python 2, it will not work
commit a8d4aa6f763599bbd8ea36ef98b7b4931bf326dc
Author: Ben McGinnes <ben at adversary.org>
Date: Fri Oct 5 02:38:14 2018 +1000
docs: org to texinfo whitspace bug
* replaced "." in headings with "·" to prevent whitspace being
appended by texinfo and breaking git.
diff --git a/lang/python/doc/src/short-history.org b/lang/python/doc/src/short-history.org
index 31b7d44..587cb9f 100644
--- a/lang/python/doc/src/short-history.org
+++ b/lang/python/doc/src/short-history.org
@@ -129,7 +129,7 @@ SWIG itself, which are worth noting here.
1. gpg (1.8.0) - Python bindings for GPGME GnuPG cryptography library
2. pyme (0.9.0) - Python support for GPGME GnuPG cryptography library
-*** GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library
+*** GPG 1·8·0 - Python bindings for GPGME GnuPG cryptography library
:PROPERTIES:
:CUSTOM_ID: pypi-gpgme-180
:END:
@@ -144,7 +144,7 @@ SWIG itself, which are worth noting here.
module and instead installing the current version of GPGME along
with the Python bindings included with that package.
-*** PyME 0.9.0 - Python support for GPGME GnuPG cryptography library
+*** PyME 0·9·0 - Python support for GPGME GnuPG cryptography library
:PROPERTIES:
:CUSTOM_ID: pypi-gpgme-90
:END:
commit 0b5930b276186afd1ca1dd91d82db7e60dd20606
Author: Ben McGinnes <ben at adversary.org>
Date: Fri Oct 5 02:30:20 2018 +1000
docs: python
* Fixed an error in the new index page and then exported to the other
two "source" formats.
diff --git a/lang/python/doc/rst/gpgme-python-howto.rst b/lang/python/doc/rst/gpgme-python-howto.rst
index f29727e..9181491 100644
--- a/lang/python/doc/rst/gpgme-python-howto.rst
+++ b/lang/python/doc/rst/gpgme-python-howto.rst
@@ -248,8 +248,8 @@ The PyME package maintained by Martin Albrecht
This package is the origin of these bindings, though they are somewhat
different now. For details of when and how the PyME package was folded
-back into GPGME itself see the *Short History* document [1]_ in the
-Python bindings ``docs`` directory. [2]_
+back into GPGME itself see the `Short History <short-history.org>`__
+document. [1]_
The PyME package was first released in 2002 and was also the first
attempt to implement a low level binding to GPGME. In doing so it
@@ -354,7 +354,7 @@ For Python 2 it checks for these executables in this order: ``python``,
``python2`` and ``python2.7``.
For Python 3 it checks for these executables in this order: ``python3``,
-``python3.7``, ``python3.6``, ``python3.5`` and ``python3.4``. [3]_
+``python3.7``, ``python3.6``, ``python3.5`` and ``python3.4``. [2]_
On systems where ``python`` is actually ``python3`` and not ``python2``
it may be possible that ``python2`` may be overlooked, but there have
@@ -411,7 +411,7 @@ directory missing a lot of expected files. Even when this occurs, the
solution is actually quite simple and will always work.
That solution is simply to run the following commands as either the
-**root** user or prepended with ``sudo -H``\ [4]_ in the
+**root** user or prepended with ``sudo -H``\ [3]_ in the
``lang/python/`` directory:
.. code:: shell
@@ -1880,7 +1880,7 @@ Encrypting to multiple keys essentially just expands upon the key
selection process and the recipients from the previous examples.
The following example encrypts a message (``text``) to everyone with an
-email address on the ``gnupg.org`` domain, [5]_ but does *not* encrypt
+email address on the ``gnupg.org`` domain, [4]_ but does *not* encrypt
to a default key or other key which is configured to normally encrypt
to.
@@ -2838,7 +2838,7 @@ module instead. It has since been modified to provide support for Python
Since it rewrites the ``hkp`` protocol prefix as ``http`` and ``hkps``
as ``https``, the module is able to be used even with servers which do
-not support the full scope of keyserver functions. [6]_ It also works
+not support the full scope of keyserver functions. [5]_ It also works
quite readily when incorporated into a `Cython <#cython>`__ generated
and compiled version of any code.
@@ -2968,9 +2968,6 @@ Footnotes
``short-history.org`` and/or ``short-history.html``.
.. [2]
- The ``lang/python/docs/`` directory in the GPGME source.
-
-.. [3]
With no issues reported specific to Python 3.7, the release of Python
3.7.1 at around the same time as GPGME 1.12.0 and the testing with
Python 3.7.1rc1, there is no reason to delay moving 3.7 ahead of 3.6
@@ -2978,7 +2975,7 @@ Footnotes
always enforce their own policies anyway and installation to each
supported minor release is quite possible too.
-.. [4]
+.. [3]
Yes, even if you use virtualenv with everything you do in Python. If
you want to install this module as just your user account then you
will need to manually configure, compile and install the *entire*
@@ -2987,13 +2984,13 @@ Footnotes
circumstances under which it is worthwhile, but generally only on
POSIX systems which utilise single user mode (some even require it).
-.. [5]
+.. [4]
You probably don\'t really want to do this. Searching the keyservers
for \"gnupg.org\" produces over 400 results, the majority of which
aren\'t actually at the gnupg.org domain, but just included a comment
regarding the project in their key somewhere.
-.. [6]
+.. [5]
Such as with ProtonMail servers. This also means that restricted
servers which only advertise either HTTP or HTTPS end points and not
HKP or HKPS end points must still be identified as as HKP or HKPS
diff --git a/lang/python/doc/rst/index.rst b/lang/python/doc/rst/index.rst
new file mode 100644
index 0000000..31dc146
--- /dev/null
+++ b/lang/python/doc/rst/index.rst
@@ -0,0 +1,12 @@
+.. _index:
+
+GPGME Python Bindings
+=====================
+
+.. _index-contents:
+
+Contents
+--------
+
+- `A short history of the project <short-history.org>`__
+- `GPGME Python Bindings HOWTO <gpgme-python-howto.org>`__
diff --git a/lang/python/doc/src/gpgme-python-howto.org b/lang/python/doc/src/gpgme-python-howto.org
index 6eba29e..caa8e2f 100644
--- a/lang/python/doc/src/gpgme-python-howto.org
+++ b/lang/python/doc/src/gpgme-python-howto.org
@@ -7,7 +7,6 @@
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \setmainfont[Ligatures={Common}]{Times New Roman}
#+LATEX_HEADER: \author{Ben McGinnes <ben at gnupg.org>}
-#+HTML_HEAD_EXTRA: <link type="application/rss+xml" href="https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=rss;f=lang/python/docs/GPGMEpythonHOWTOen.org"/>
* Introduction
@@ -254,8 +253,7 @@ version 3.0 (or any later version).
This package is the origin of these bindings, though they are somewhat
different now. For details of when and how the PyME package was
-folded back into GPGME itself see the /Short History/ document[fn:1]
-in the Python bindings =docs= directory.[fn:2]
+folded back into GPGME itself see the [[file:short-history.org][Short History]] document.[fn:1]
The PyME package was first released in 2002 and was also the first
attempt to implement a low level binding to GPGME. In doing so it
@@ -365,7 +363,7 @@ For Python 2 it checks for these executables in this order: =python=,
=python2= and =python2.7=.
For Python 3 it checks for these executables in this order: =python3=,
- =python3.7=, =python3.6=, =python3.5= and =python3.4=.[fn:3]
+ =python3.7=, =python3.6=, =python3.5= and =python3.4=.[fn:2]
On systems where =python= is actually =python3= and not =python2= it
may be possible that =python2= may be overlooked, but there have been
@@ -425,7 +423,7 @@ build directory missing a lot of expected files. Even when this
occurs, the solution is actually quite simple and will always work.
That solution is simply to run the following commands as either the
-*root* user or prepended with =sudo -H=[fn:4] in the =lang/python/=
+*root* user or prepended with =sudo -H=[fn:3] in the =lang/python/=
directory:
#+BEGIN_SRC shell
@@ -1928,7 +1926,7 @@ Encrypting to multiple keys essentially just expands upon the key
selection process and the recipients from the previous examples.
The following example encrypts a message (=text=) to everyone with an
-email address on the =gnupg.org= domain,[fn:5] but does /not/ encrypt
+email address on the =gnupg.org= domain,[fn:4] but does /not/ encrypt
to a default key or other key which is configured to normally encrypt
to.
@@ -2899,7 +2897,7 @@ support for Python 2.7 as well and is available via PyPI.
Since it rewrites the =hkp= protocol prefix as =http= and =hkps= as
=https=, the module is able to be used even with servers which do not
-support the full scope of keyserver functions.[fn:6] It also works quite
+support the full scope of keyserver functions.[fn:5] It also works quite
readily when incorporated into a [[#cython][Cython]] generated and compiled version
of any code.
@@ -3018,16 +3016,14 @@ PURPOSE.
[fn:1] =short-history.org= and/or =short-history.html=.
-[fn:2] The =lang/python/docs/= directory in the GPGME source.
-
-[fn:3] With no issues reported specific to Python 3.7, the release of
+[fn:2] With no issues reported specific to Python 3.7, the release of
Python 3.7.1 at around the same time as GPGME 1.12.0 and the testing
with Python 3.7.1rc1, there is no reason to delay moving 3.7 ahead of
3.6 now. Production environments with more conservative requirements
will always enforce their own policies anyway and installation to each
supported minor release is quite possible too.
-[fn:4] Yes, even if you use virtualenv with everything you do in
+[fn:3] Yes, even if you use virtualenv with everything you do in
Python. If you want to install this module as just your user account
then you will need to manually configure, compile and install the
/entire/ GnuPG stack as that user as well. This includes libraries
@@ -3035,12 +3031,12 @@ which are not often installed that way. It can be done and there are
circumstances under which it is worthwhile, but generally only on
POSIX systems which utilise single user mode (some even require it).
-[fn:5] You probably don't really want to do this. Searching the
+[fn:4] You probably don't really want to do this. Searching the
keyservers for "gnupg.org" produces over 400 results, the majority of
which aren't actually at the gnupg.org domain, but just included a
comment regarding the project in their key somewhere.
-[fn:6] Such as with ProtonMail servers. This also means that
+[fn:5] Such as with ProtonMail servers. This also means that
restricted servers which only advertise either HTTP or HTTPS end
points and not HKP or HKPS end points must still be identified as as
HKP or HKPS within the Python Code. The =hkp4py= module will rewrite
diff --git a/lang/python/doc/src/index.org b/lang/python/doc/src/index.org
index 8410c40..701d986 100644
--- a/lang/python/doc/src/index.org
+++ b/lang/python/doc/src/index.org
@@ -21,6 +21,5 @@
:END:
-- [[short-history][A short history of the project]]
-- [[gpgme-python-howto][GPGME Python Bindings HOWTO]]
-
+- [[file:short-history.org][A short history of the project]]
+- [[file:gpgme-python-howto.org][GPGME Python Bindings HOWTO]]
diff --git a/lang/python/doc/texinfo/gpgme-python-howto.texi b/lang/python/doc/texinfo/gpgme-python-howto.texi
index b474242..40beb7a 100644
--- a/lang/python/doc/texinfo/gpgme-python-howto.texi
+++ b/lang/python/doc/texinfo/gpgme-python-howto.texi
@@ -418,8 +418,7 @@ version 3.0 (or any later version).
This package is the origin of these bindings, though they are somewhat
different now. For details of when and how the PyME package was
-folded back into GPGME itself see the @emph{Short History} document at footnote{@samp{short-history.org} and/or @samp{short-history.html}.}
-in the Python bindings @samp{docs} directory. at footnote{The @samp{lang/python/docs/} directory in the GPGME source.}
+folded back into GPGME itself see the @uref{short-history.org, Short History} document. at footnote{@samp{short-history.org} and/or @samp{short-history.html}.}
The PyME package was first released in 2002 and was also the first
attempt to implement a low level binding to GPGME. In doing so it
diff --git a/lang/python/doc/texinfo/index.texi b/lang/python/doc/texinfo/index.texi
new file mode 100644
index 0000000..4f80423
--- /dev/null
+++ b/lang/python/doc/texinfo/index.texi
@@ -0,0 +1,52 @@
+\input texinfo @c -*- texinfo -*-
+ at c %**start of header
+ at setfilename index.info
+ at settitle GNU Privacy Guard (GnuPG) Made Easy Python Bindings
+ at documentencoding UTF-8
+ at documentlanguage en
+ at c %**end of header
+
+ at finalout
+ at titlepage
+ at title GNU Privacy Guard (GnuPG) Made Easy Python Bindings
+ at author Ben McGinnes
+ at end titlepage
+
+ at contents
+
+ at ifnottex
+ at node Top
+ at top GNU Privacy Guard (GnuPG) Made Easy Python Bindings
+ at end ifnottex
+
+ at menu
+* GPGME Python Bindings::
+
+ at detailmenu
+--- The Detailed Node Listing ---
+
+GPGME Python Bindings
+
+* Contents::
+
+ at end detailmenu
+ at end menu
+
+ at node GPGME Python Bindings
+ at chapter GPGME Python Bindings
+
+ at menu
+* Contents::
+ at end menu
+
+ at node Contents
+ at section Contents
+
+ at itemize
+ at item
+ at uref{short-history.org, A short history of the project}
+ at item
+ at uref{gpgme-python-howto.org, GPGME Python Bindings HOWTO}
+ at end itemize
+
+ at bye
\ No newline at end of file
diff --git a/lang/python/doc/texinfo/short-history.texi b/lang/python/doc/texinfo/short-history.texi
index 2854d91..fd136b5 100644
--- a/lang/python/doc/texinfo/short-history.texi
+++ b/lang/python/doc/texinfo/short-history.texi
@@ -40,8 +40,8 @@ Relics of the past
The Perils of PyPI
-* GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library: GPG 180 - Python bindings for GPGME GnuPG cryptography library.
-* PyME 0.9.0 - Python support for GPGME GnuPG cryptography library: PyME 090 - Python support for GPGME GnuPG cryptography library.
+* GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library: GPG 180 - Python bindings for GPGME GnuPG cryptography library.
+* PyME 0.9.0 - Python support for GPGME GnuPG cryptography library: PyME 090 - Python support for GPGME GnuPG cryptography library.
@end detailmenu
@end menu
@@ -172,8 +172,8 @@ pyme (0.9.0) - Python support for GPGME GnuPG cryptography library
@end enumerate
@menu
-* GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library: GPG 180 - Python bindings for GPGME GnuPG cryptography library.
-* PyME 0.9.0 - Python support for GPGME GnuPG cryptography library: PyME 090 - Python support for GPGME GnuPG cryptography library.
+* GPG 1.8.0 - Python bindings for GPGME GnuPG cryptography library: GPG 180 - Python bindings for GPGME GnuPG cryptography library.
+* PyME 0.9.0 - Python support for GPGME GnuPG cryptography library: PyME 090 - Python support for GPGME GnuPG cryptography library.
@end menu
@node GPG 180 - Python bindings for GPGME GnuPG cryptography library
@@ -206,4 +206,4 @@ For those using Python 2, there is essentially no harm in using
this module, but it may lack a number of more recent features
added to GPGME.
- at bye
+ at bye
\ No newline at end of file
commit 48258879720a4f423d0efa955da942d69f3c49d4
Author: Ben McGinnes <ben at adversary.org>
Date: Fri Oct 5 01:47:56 2018 +1000
docs: python
* lang/python/doc/meta/TODO.org: Added the two major documentation
build system tasks to the TODO list.
* Added an index page in preparation for sorting out the second of
those TODO lists (Docutils is a lot easier to handle than Texinfo).
* Meanwhile, have confirmed that it all builds just fine under
GNU/Linux, OS X and FreeBSD while retaining the documentation, so
that's a nice improvement from 1.11.1.
Tested-by: Ben McGinnes <ben at adversary.org>
Signed-off-by: Ben McGinnes <ben at adversary.org>
diff --git a/lang/python/doc/meta/TODO.org b/lang/python/doc/meta/TODO.org
index add8f4f..0be99b3 100644
--- a/lang/python/doc/meta/TODO.org
+++ b/lang/python/doc/meta/TODO.org
@@ -29,6 +29,38 @@
through converting to either Markdown or XHTML first.
+** TODO Documentation build systems
+ :PROPERTIES:
+ :CUSTOM_ID: todo-docs-build-systems
+ :END:
+
+Though Org Mode is being used for the default documentation format, it
+still needs to end up as usable by end users. So the Org Mode files
+are used to produce the "source" files used by the two main contenders
+for documenting the bindings: Texinfo and ReStructuredText/Docutils.
+
+
+*** TODO Texinfo documentation
+ :PROPERTIES:
+ :CUSTOM_ID: todo-docs-build-texinfo
+ :END:
+
+Need to add all of Texinfo's ... special systems to make it do its
+things.
+
+
+*** TODO ReStructuredText documentation
+ :PROPERTIES:
+ :CUSTOM_ID: todo-docs-build-docutils
+ :END:
+
+Need to run Sphinx's quick start, add it to the requirements and tweak
+the index page for the rst files to point to the HOWTO and other files.
+
+It might just be easier to do all that in Org Mode and convert the
+lot, then the Sphinx bits can be automated.
+
+
** STARTED Documentation HOWTO
:PROPERTIES:
:CUSTOM_ID: todo-docs-howto
diff --git a/lang/python/doc/src/index.org b/lang/python/doc/src/index.org
new file mode 100644
index 0000000..8410c40
--- /dev/null
+++ b/lang/python/doc/src/index.org
@@ -0,0 +1,26 @@
+#+TITLE: GNU Privacy Guard (GnuPG) Made Easy Python Bindings
+#+AUTHOR: Ben McGinnes
+#+LATEX_COMPILER: xelatex
+#+LATEX_CLASS: article
+#+LATEX_CLASS_OPTIONS: [12pt]
+#+LATEX_HEADER: \usepackage{xltxtra}
+#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
+#+LATEX_HEADER: \setmainfont[Ligatures={Common}]{Times New Roman}
+#+LATEX_HEADER: \author{Ben McGinnes <ben at gnupg.org>}
+
+
+* GPGME Python Bindings
+ :PROPERTIES:
+ :CUSTOM_ID: index
+ :END:
+
+
+** Contents
+ :PROPERTIES:
+ :CUSTOM_ID: index-contents
+ :END:
+
+
+- [[short-history][A short history of the project]]
+- [[gpgme-python-howto][GPGME Python Bindings HOWTO]]
+
-----------------------------------------------------------------------
Summary of changes:
lang/python/doc/meta/TODO.org | 32 +++++++++++++++
lang/python/doc/rst/gpgme-python-howto.rst | 21 +++++-----
lang/python/doc/rst/index.rst | 12 ++++++
lang/python/doc/rst/short-history.rst | 14 +++----
lang/python/doc/src/gpgme-python-howto.org | 22 +++++------
lang/python/doc/src/index.org | 25 ++++++++++++
lang/python/doc/src/short-history.org | 4 +-
lang/python/doc/texinfo/gpgme-python-howto.texi | 3 +-
lang/python/doc/texinfo/index.texi | 52 +++++++++++++++++++++++++
lang/python/doc/texinfo/short-history.texi | 18 ++++-----
10 files changed, 158 insertions(+), 45 deletions(-)
create mode 100644 lang/python/doc/rst/index.rst
create mode 100644 lang/python/doc/src/index.org
create mode 100644 lang/python/doc/texinfo/index.texi
hooks/post-receive
--
GnuPG Made Easy
http://git.gnupg.org
More information about the Gnupg-commits
mailing list