gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: use ‘.. code-block:: c’ (three insta


From: gnunet
Subject: [taler-docs] branch master updated: use ‘.. code-block:: c’ (three instances)
Date: Fri, 04 Dec 2020 10:32:34 +0100

This is an automated email from the git hooks/post-receive script.

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new b7cf1cb  use ‘.. code-block:: c’ (three instances)
b7cf1cb is described below

commit b7cf1cb38dcfa05f06acdc2cc1371ffc0375ed8b
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Dec 4 04:31:15 2020 -0500

    use ‘.. code-block:: c’ (three instances)
---
 taler-exchange-manual.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 4d19709..e68bdf8 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -850,7 +850,7 @@ starting time at which the signing key can be used in 
microseconds since
 the Epoch. The file format is defined by the struct
 TALER_EXCHANGEDB_PrivateSigningKeyInformationP:
 
-::
+.. code-block:: c
 
    struct TALER_EXCHANGEDB_PrivateSigningKeyInformationP {
       struct TALER_ExchangePrivateKeyP signkey_priv;
@@ -883,7 +883,7 @@ struct TALER_EXCHANGEDB_DenominationKeyInformationP giving 
the
 attributes of the denomination key and the associated signature with the
 exchange’s long-term offline key:
 
-::
+.. code-block:: c
 
    struct TALER_EXCHANGEDB_DenominationKeyInformationP {
      struct TALER_MasterSignatureP signature;
@@ -940,7 +940,7 @@ Each file must contain a header with the public key 
information of the
 auditor, the master public key of the exchange, and the number of signed
 denomination keys:
 
-::
+.. code-block:: c
 
    struct AuditorFileHeaderP {
      struct TALER_AuditorPublicKeyP apub;

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]