gnunet-svn
[Top][All Lists]
Advanced

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

[taler-docs] branch master updated: recommend ‘dev/$USER/...’ as "person


From: gnunet
Subject: [taler-docs] branch master updated: recommend ‘dev/$USER/...’ as "personal" branch name
Date: Wed, 09 Dec 2020 06:01:49 +0100

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

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new f1dd55b  recommend ‘dev/$USER/...’ as "personal" branch name
f1dd55b is described below

commit f1dd55b4c70ab8a124a0c2f90c5c7889f0d6f51d
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Wed Dec 9 00:00:15 2020 -0500

    recommend ‘dev/$USER/...’ as "personal" branch name
---
 developers-manual.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/developers-manual.rst b/developers-manual.rst
index 337e986..f176cbe 100644
--- a/developers-manual.rst
+++ b/developers-manual.rst
@@ -107,7 +107,8 @@ to sign them, you can retroactively add signatures using:
    $ git rebase -S
 
 
-Whether you commit to a personal branch, a feature branch or to ``master`` 
should
+Whether you commit to a personal branch (recommended: ``dev/$USER/...``),
+a feature branch or to ``master`` should
 depend on your level of comfort and the nature of the change.  As a general
 rule, the code in ``master`` must always build and tests should always pass, at
 least on your own system. However, we all make mistakes and you should expect

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