From: John Levon <movement@us...> - 2003-02-22 19:53:43
Update of /cvsroot/oprofile/oprofile
In directory sc8-pr-cvs1:/tmp/cvs-serv31078
say something about patches and cvs
RCS file: /cvsroot/oprofile/oprofile/HACKING,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- HACKING 17 Jan 2003 03:57:18 -0000 1.1
+++ HACKING 22 Feb 2003 19:53:41 -0000 1.2
@@ -73,3 +73,21 @@
We still currently support gcc 2.91.66. Please bear this in mind.
+Making patches, commit rights
+Patches should be in diff -u format, appliable by patch -p1 in the top-level
+source directory. Patches should not include changes to generated files.
+Even trivial patches must have a change log entry in the usual format (see
+ChangeLog). Refer to bug numbers in the change log if relevant.
+You may after a while be given direct commit rights. You should be subscribed
+to both the main list and the commits mailing list if you do. Your cvs commit
+message only needs to briefly describe what your change does - the change log
+should have the detailed description. Any non-trivial change needs approval
+from either John or Phil, unless stated otherwise. The CVS tree will freeze
+occassionally for release, in which case no commits are allowed at all without
+agreement of John and Phil.