gnunet-svn
[Top][All Lists]
Advanced

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

[taler-exchange] branch master updated: work around indentation bug of u


From: gnunet
Subject: [taler-exchange] branch master updated: work around indentation bug of uncrustify
Date: Sun, 01 Mar 2020 14:05:40 +0100

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

grothoff pushed a commit to branch master
in repository exchange.

The following commit(s) were added to refs/heads/master by this push:
     new c11475c0 work around indentation bug of uncrustify
c11475c0 is described below

commit c11475c081afcd5ccc667451b9383510fd42cf1b
Author: Christian Grothoff <address@hidden>
AuthorDate: Sun Mar 1 14:05:38 2020 +0100

    work around indentation bug of uncrustify
---
 src/exchange/taler-exchange-httpd_responses.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/exchange/taler-exchange-httpd_responses.c 
b/src/exchange/taler-exchange-httpd_responses.c
index 9795d61a..f2593672 100644
--- a/src/exchange/taler-exchange-httpd_responses.c
+++ b/src/exchange/taler-exchange-httpd_responses.c
@@ -270,7 +270,8 @@ TEH_RESPONSE_compile_transaction_history (const struct
            the denomination key's RSA signature over coin_pub, but as the
            wallet should really already have this information (and cannot
            check or do anything with it anyway if it doesn't), it seems
-           strictly unnecessary. */if (0 !=
+           strictly unnecessary. *///
+        if (0 !=
             json_array_append_new (history,
                                    json_pack ("{s:s, s:o, s:o, s:o, s:o, s:o}",
                                               "type", "OLD-COIN-RECOUP",
@@ -373,7 +374,8 @@ TEH_RESPONSE_compile_transaction_history (const struct
            hash and the denomination key's RSA signature over coin_pub, but as
            the wallet should really already have this information (and cannot
            check or do anything with it anyway if it doesn't), it seems
-           strictly unnecessary. */if (0 !=
+           strictly unnecessary. *///
+        if (0 !=
             json_array_append_new (history,
                                    json_pack ("{s:s, s:o, s:o, s:o, s:o, s:o}",
                                               "type", "RECOUP-REFRESH",

-- 
To stop receiving notification emails like this one, please contact
address@hidden.



reply via email to

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