gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [taler-docs] branch master updated: fix link, fix bug track


From: gnunet
Subject: [GNUnet-SVN] [taler-docs] branch master updated: fix link, fix bug tracker section.
Date: Thu, 10 Oct 2019 11:24:20 +0200

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

ng0 pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 4c0f850  fix link, fix bug tracker section.
4c0f850 is described below

commit 4c0f850a6c82fc7a3c4cf90a9c9113fb5cac3f3e
Author: ng0 <address@hidden>
AuthorDate: Thu Oct 10 09:23:59 2019 +0000

    fix link, fix bug tracker section.
---
 onboarding.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/onboarding.rst b/onboarding.rst
index d8f4571..77c8d51 100644
--- a/onboarding.rst
+++ b/onboarding.rst
@@ -367,7 +367,7 @@ Python code should be written and build against version 3.7 
of Python.
 Style
 -----
 
-We use `yapf <https://github.com/google/yapf>` to reformat the
+We use `yapf <https://github.com/google/yapf>`_ to reformat the
 code to conform to our style instructions.
 A reusable yapf style file can be found in ``taler-build-scripts``,
 which is intended to be used as a git submodule.
@@ -378,9 +378,9 @@ Bugtracking
 ===========
 
 Bug tracking is done with Mantis (https://www.mantisbt.org/). All the
-bugs are then showed and managed at ``https://bugs.gnunet.org/``, under
+bugs are displayed and managed at ``https://bugs.gnunet.org/``, under
 the "Taler" project. A registration on the Web site is needed in order
-to use the bug tracker.
+to use the bug tracker, only read access is granted without a login.
 
 .. _Continuous-integration:
 

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



reply via email to

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