2002-07-19 Tim Coleman <tim@timcoleman.com>

[mono.git] / doc / ccvs

diff --git a/doc/ccvs b/doc/ccvs
index 274d7d9afdf4ff55e7f91cdd9295baed90ee7c48..c7710b5660166c63600bf29d70a207add733d393 100644 (file)
--- a/doc/ccvs
+++ b/doc/ccvs
@@ -67,6 +67,25 @@
        mail mono-list@ximian.com < file.diff
 </pre>
 
+** Keeping track of changes.
+
+       We provide two e-mail based mechanisms to keep track of
+       changes to the code base:
+       
+       <ul>
+               * <a href="mailto:mono-patches-request@ximian.com">
+                 mono-patches@ximian.com</a>: This mailing list receives
+                 in patch form all the changes that are being made to the
+                 CVS.
+
+               * <a href="mailto:mono-cvs-list-request@ximian.com">
+                 mono-cvs-list@ximian.com</a>: This mailing list only
+                 receives the CVS commit logs with a list of files
+                 modified.
+       </ul>
+
+       We hope to offer LXR and Bonsai in the future as well.
+
 ** Commiting your work
 
        Once you get approval to commit to the CVS, or if you are
@@ -100,9 +119,13 @@
 ** Recommendations
 
        Please do not commit code that would break the compile to the
-       CVS, because that normally wastes everybody's time.  
+       CVS, because that normally wastes everybody's time.  Two things 
+       are important in this step: trying to build your sources and making 
+       sure that you add all the new files before you do a commit.
 
-       Make sure that you add all the files before you do a commit.
+       To build the sources, most of the type trying the `make' command
+       is enough.  In some cases (the class libraries) we use nant, so
+       you need to run nant manually.
 
        Use ChangeLog entries so we can keep textual descriptions of
        your work, and use the contents of your ChangeLog file as the