taler-deployment

Deployment scripts and configuration files
Log | Files | Refs | README

commit ac7cfa355d3291cb7550518ba2e205d49ef39967
parent 1f483af4ae575075fb7a1c65f92a8b60025500bd
Author: Marcello Stanisci <stanisci.m@gmail.com>
Date:   Mon, 10 Jun 2019 21:05:36 +0200

remove a few \n\n

Diffstat:
Mdoc/onboarding.texi | 4----
1 file changed, 0 insertions(+), 4 deletions(-)

diff --git a/doc/onboarding.texi b/doc/onboarding.texi @@ -402,7 +402,6 @@ if (GNUNET_OK != TALER_TESTING_get_trait_amount_obj (cmd2, 0, &a)) use(a); /* 'a' points straight into the internal state of CMD2 */ @end example - In the Taler realm, there is also the possibility to alter the behaviour of supposedly well-behaved components. This is needed when, for example, we want the exchange to return some corrupted @@ -415,7 +414,6 @@ programmed to tamper with the data exchanged by A and B. Please refer to the Twister codebase (under the @code{test} directory) in order to see how to configure it. - @node Releases @chapter Releases @@ -458,7 +456,6 @@ should be the change of the version. For the exchange test cases to pass, @code{make install} must be run first. Without it, test cases will fail because plugins can't be located. - @example ./bootstrap ./configure # add required options for your system @@ -468,7 +465,6 @@ cd taler-$COMPONENT-$VERSION make install check @end example - @section Wallet WebExtension The version of the wallet is in @emph{manifest.json}. The @code{version_name} should be