fnux/cdist
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

comment about conf/manifest/init in cdist-hacker

Browse source 
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
This commit is contained in:
Nico Schottelius 2011-03-24 15:58:47 +01:00
commit c72833ce74
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/man/cdist-hacker.text
View file

@ -27,6 +27,12 @@ read the scripts bin/cdist-deploy-to calls. The magnificent HACKERS_README
may be of great help as well. may be of great help as well.
CODING CONVENTIONS (CORE)
-------------------------
- All variables exported by cdist are prefixed with a double underscore (__)
- All cdist-internal variables are prefixed with __cdist_ and are generally not exported.
HOW TO SUBMIT STUFF FOR INCLUSION INTO UPSTREAM CDIST HOW TO SUBMIT STUFF FOR INCLUSION INTO UPSTREAM CDIST
----------------------------------------------------- -----------------------------------------------------
If you did some cool changes to cdist, which you value as a benefit for If you did some cool changes to cdist, which you value as a benefit for
@ -40,6 +46,8 @@ work nor kill the authors brain:
- Exception: Bugfixes to a version branch - Exception: Bugfixes to a version branch
- Code submissions must be in your master branch - Code submissions must be in your master branch
- Exception: If you only want a comment on your code, but not an inclusion. - Exception: If you only want a comment on your code, but not an inclusion.
- Do not add conf/manifest/init - This file should only be touched in your
private branch!
As soon as your work meets these requirements, you can contact me As soon as your work meets these requirements, you can contact me
(IRC, Mailinglist, Phone, RFC 1149) and I'll check your code before (IRC, Mailinglist, Phone, RFC 1149) and I'll check your code before