Index: openacs-4/packages/acs-core-docs/www/cvs-guidelines.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-guidelines.html,v diff -u -r1.10.2.10 -r1.10.2.11 --- openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 21 Jun 2016 07:44:35 -0000 1.10.2.10 +++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 23 Jun 2016 08:32:45 -0000 1.10.2.11 @@ -44,7 +44,7 @@ ~/.cvsrc with the contents: 

cvs -z6
 cvs -q

-z6 speeds up cvs access over the network quite a bit by enabling compressed - connection by default. -q suppresses some verbose output from commands. For example, it makes the output of cvs up much easier to read.

Administrator Note: These are the steps to grant CVS commit rights to a user:

  1. Create the user's account. On cvs.openacs.org:

    sudo bash
+        connection by default.  -q suppresses some verbose output from commands.  For example, it makes the output of cvs up much easier to read.
    Administrator Note: These are the steps to grant CVS commit rights to a user:
    1. Create the user's account.  On cvs.openacs.org:
      sudo bash
 /usr/sbin/useradd -c "Real Name" -G cvs -p passwd username
 /usr/sbin/usermod -G cvs,username username
           
    2. Grant cvs access to the user account.  On any machine, in a temporary directory:
      cvs -d :ext:cvs.openacs.org:/cvsroot co CVSROOT
@@ -131,7 +131,7 @@
                   calendar package. All non-core, non-dotlrn packages should have a
                   tag of this style, based on the package name. Many packages have
                   not been re-released since the new naming convention was adopted
-                  and so don't have a tag of this type.
+                  and so don't have a tag of this type.
                 
    3. openacs-x-y-compat tags point to the most recent released version of OpenACS X.Y.
             It is similar to openacs-x-y-z-compat, except that it will
             always get the most recent dot-release of Core and the
@@ -229,9 +229,9 @@
         be addressed with another upgrade script. E.g., the last planned
         upgrade script for a package previously in dev 1 would be
         upgrade-2.0.0d1-2.0.0b1.sql, not upgrade-2.0.0d1-2.0.0.sql. Note
-        that using rc1 instead of b1 would be nice, because that's the
+        that using rc1 instead of b1 would be nice, because that's the
         convention with release codes in cvs, but the package manager
-        doesn't support rc tags.
+        doesn't support rc tags.
       
    4. 
               Database upgrade scripts should never go to the release
               version, e.g., should always have a letter suffix such as d1 or
@@ -310,9 +310,9 @@
         OpenACS code so that patches can be generated.
         
       
    
-          For example, adding a new API function wouldn't require a
+          For example, adding a new API function wouldn't require a
           TIP. Changing an existing API function by adding an optional new
-          flag which defaults to no-effect wouldn't require a TIP. Added a
+          flag which defaults to no-effect wouldn't require a TIP. Added a
           new mandatory flag to an existing function would require a
           TIP.

@@ -366,10 +366,10 @@ Added missing h3 HTML close tag".

  • Commit one cohesive bug fix or feature change at a time. - Don't put a bunch of unrelated changes into one commit. + Don't put a bunch of unrelated changes into one commit.

  • Before you throw out or change a piece of code that you - don't fully understand, use cvs annotate and cvs log on the file to + don't fully understand, use cvs annotate and cvs log on the file to see who wrote the code and why. Consider contacting the author.

  • @@ -395,7 +395,7 @@ OpenACS cvs web and - Jeff's cvs + Jeff's cvs browser are useful tools in understanding what is @@ -416,7 +416,7 @@

  • file locking etc. with cvs

  • - Piskorski's cvs refs + Piskorski's cvs refs

  • backup with cvs