[GNUnet-SVN] [taler-api] branch master updated: fix some compiler warnings

[gnunet]

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

marcello pushed a commit to branch master
in repository api.

The following commit(s) were added to refs/heads/master by this push:
     new d0bf7ea  fix some compiler warnings
d0bf7ea is described below

commit d0bf7ea6b806a404df68c6447a136c8441a3a54a
Author: Marcello Stanisci <address@hidden>
AuthorDate: Thu Jun 1 09:38:34 2017 +0200

    fix some compiler warnings
---
 api-bank.rst                          |   6 ++----
 api-exchange.rst                      |  18 +++++++++---------
 api-merchant.rst                      |   3 +--
 exts/__pycache__/tsref.cpython-35.pyc | Bin 7457 -> 7453 bytes
 4 files changed, 12 insertions(+), 15 deletions(-)

diff --git a/api-bank.rst b/api-bank.rst
index 6068176..401847f 100644
--- a/api-bank.rst
+++ b/api-bank.rst
@@ -36,10 +36,8 @@ request.
 
 **Response:**
 
-:status 200 OK: The request has been correctly handled, so the funds have been 
transferred to the recipient's account.  The body is a
-`BankDepositDetails`_.
-
-:status 400 Bad Request: The bank replies a `BankError`_ object
+:status 200 OK: The request has been correctly handled, so the funds have been 
transferred to the recipient's account.  The body is a `BankDepositDetails`_.
+:status 400 Bad Request: The bank replies a `BankError`_ object.
 
 **Details:**
 
diff --git a/api-exchange.rst b/api-exchange.rst
index caf9ee0..4399b48 100644
--- a/api-exchange.rst
+++ b/api-exchange.rst
@@ -1058,18 +1058,18 @@ in using this API.
 
   **Response:**
   :status 200 OK:
-    The request was succesful, and the response is a `PaybackConfirmation`.
-    Note that repeating exactly the same request
-    will again yield the same response, so if the network goes down during the
-    transaction or before the client can commit the coin signature to disk, the
-    coin is not lost.
+  The request was succesful, and the response is a `PaybackConfirmation`.
+  Note that repeating exactly the same request
+  will again yield the same response, so if the network goes down during the
+  transaction or before the client can commit the coin signature to disk, the
+  coin is not lost.
   :status 401 Unauthorized: The coin's signature is invalid.
   :status 403 Forbidden: The coin was already used for payment.
-    The response is a `DepositDoubleSpendError`_.
+  The response is a `DepositDoubleSpendError`_.
   :status 404 Not Found:
-    The denomination key is not in the set of denomination
-    keys where emergency pay back is enabled, or the blinded
-    coin is not known to have been withdrawn.
+  The denomination key is not in the set of denomination
+  keys where emergency pay back is enabled, or the blinded
+  coin is not known to have been withdrawn.
 
   **Details:**
 
diff --git a/api-merchant.rst b/api-merchant.rst
index ede3370..e8eafdf 100644
--- a/api-merchant.rst
+++ b/api-merchant.rst
@@ -151,8 +151,6 @@ The following API are made available by the merchant's 
`backend` to the merchant
 
   **Request:**
 
-.. _proposal:
-
   The backend expects an `order` as input.  The order is a `ProposalData`_
   object **without** the fields:
 
@@ -534,6 +532,7 @@ in the `order`, and then by signing it.  See below.
 
 The `proposal data` must have the following structure:
 
+  .. _ProposalData:
   .. _tsref-type-ProposalData:
   .. code-block:: tsref
 
diff --git a/exts/__pycache__/tsref.cpython-35.pyc 
b/exts/__pycache__/tsref.cpython-35.pyc
index 697cecf..3d2e0de 100644
Binary files a/exts/__pycache__/tsref.cpython-35.pyc and 
b/exts/__pycache__/tsref.cpython-35.pyc differ

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