[Git][NTPsec/ntpsec][master] add more Git advice to devel/hacking.txt
gitlab at mg.gitlab.com
Wed Jan 4 23:56:25 UTC 2017
Mark Atwood pushed to branch master at NTPsec / ntpsec
17e99336 by Mark Atwood at 2017-01-04T15:56:17-08:00
add more Git advice to devel/hacking.txt
- - - - -
1 changed file:
@@ -378,6 +378,23 @@ C was the minor. They also use release-candidate suffixes.
== Contribution workflow and conventions ==
+Please work on one piece of conceptual work at a time.
+Please make sure your code builds and passes the test suite before you
+commit it, and especially before you push it.
+Before starting significant work, propose it first in the
+mailto:devel at ntpsec.org mailing list. Other people may have
+suggestions, will want to collaborate, and will wish to review your
+=== Git ===
+We use Git as our distributed version control system.
+If you ever get stuck or confused while using Git, please consult
=== GitLab.com ===
We use GitLab.com as our forge.
@@ -398,14 +415,6 @@ of the Project Manager, after consulting with the existing core team.
Generally, other levels of access will not be granted, as they are not
necessary to be a welcome and effective contributor.
-Please work on one piece of conceptual work at a time. Keep each
-narrative of work each in a different branch.
-Before starting significant work, propose it first in the
-mailto:devel at ntpsec.org mailing list. Other people may have
-suggestions, will want to collaborate, and will wish to review your
=== Optional: Send patches by email ===
If you do not want to use GitLab pull requests, we welcome simple fix
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/17e993361df8abed90838ebfa3654496a2cab634
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vc