gnunet-svn
[Top][All Lists]
Advanced

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

[taler-exchange] branch master updated: clarify why FIXME does not need


From: gnunet
Subject: [taler-exchange] branch master updated: clarify why FIXME does not need fix
Date: Fri, 25 Dec 2020 09:06: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 32da8154 clarify why FIXME does not need fix
32da8154 is described below

commit 32da8154275a200144406d819d8abb77cab6fe30
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Dec 25 09:06:37 2020 +0100

    clarify why FIXME does not need fix
---
 src/lib/exchange_api_refund.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/lib/exchange_api_refund.c b/src/lib/exchange_api_refund.c
index b2f46810..3ccbd3ee 100644
--- a/src/lib/exchange_api_refund.c
+++ b/src/lib/exchange_api_refund.c
@@ -292,7 +292,7 @@ verify_conflict_history_ok (struct 
TALER_EXCHANGE_RefundHandle *rh,
         GNUNET_JSON_spec_fixed_auto ("merchant_pub",
                                      &rr.merchant),
         GNUNET_JSON_spec_uint64 ("rtransaction_id",
-                                 &rr.rtransaction_id), // FIXME: shouldn't 
this be NBO!?
+                                 &rr.rtransaction_id), /* Note: converted to 
NBO below */
         GNUNET_JSON_spec_end ()
       };
 

-- 
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]