chiark
/
gitweb
/
~ianmdlvl
/
developers-reference.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
I really mean it!
[developers-reference.git]
/
README-contrib
diff --git
a/README-contrib
b/README-contrib
index 8ecb71b5564b08ee4391597cfa812e6d58e79418..226b5a9c5a2235712993b9564638a3cc514b82b0 100644
(file)
--- a/
README-contrib
+++ b/
README-contrib
@@
-28,12
+28,19
@@
first submit a few patches as bug reports. Writing patches for
existing bugs are also always appreciated. You may wish to make
patches against the CVS sources, about which see below.
existing bugs are also always appreciated. You may wish to make
patches against the CVS sources, about which see below.
+Do not commit patches to the developers reference yourself unless
+authorized to do so. Patches need to be finalized and common opinion
+before they are applied. This is even true if you happen to have
+cvs access for other reasons.
+
* CVS
If you're interested in ongoing maintenance, once you've shown that
you've mastered the style of the manual with a couple accepted
* CVS
If you're interested in ongoing maintenance, once you've shown that
you've mastered the style of the manual with a couple accepted
-patches, you can be given CVS pserver access.
+patches, you can be given CVS pserver access. If you have already
+access to the CVS server for other reasons, do not use it unless
+authorized to do so.
Instructions on how to get the CVS version of this software, including
how to get CVS access, can be found at
Instructions on how to get the CVS version of this software, including
how to get CVS access, can be found at