--- mitgcm.org/front_content/using_cvs.xml	2003/12/04 17:02:02	1.3
+++ mitgcm.org/front_content/using_cvs.xml	2005/09/29 12:22:54	1.10
@@ -14,7 +14,6 @@
     <meta name="add_title" content="Using CVS" />
     <!-- Hinting for menu generation -->
 
-    <title>MITgcm: <!--ADDTITLE--></title>
 <style type="text/css">
  span.c2 {font-size: 110%}
  div.c1 {text-align: center}
@@ -40,7 +39,7 @@
   $ export CVSROOT=':pserver:cvsanon@mitgcm.org:/u/gcmpack'
   $ cvs login 
     ( enter the CVS password: "cvsanon" )
-  $ cvs co MITgcm MITgcm_contrib
+  $ cvs co MITgcm
 </pre>
 
     <p>Using a "C", "csh", or "tcsh" shell the commands are:</p>
@@ -49,9 +48,22 @@
   $ setenv CVSROOT ':pserver:cvsanon@mitgcm.org:/u/gcmpack'
   $ cvs login
     ( enter the CVS password: "cvsanon" )
-  $ cvs co MITgcm MITgcm_contrib
+  $ cvs co MITgcm
 </pre>
 
+    <p>A large amount of additional (optional!) content can be obtained from the
+      MITgcm_contrib directory that can be checked out using:
+
+<pre>
+  $ cvs co MITgcm_contrib
+</pre>
+
+      In general, we do not recommend checking out all of MITgcm_contrib since
+      it takes a long time to download (particularly from remote locations) and
+      much of it is specific to certain setups (eg. high-res setups,
+      in-development material that is not yet part of the "main" code,
+      etc.).</p>
+
     <p>Note that you will only need to perform the "cvs login" once.  And for
       convenience, you may want to add the CVSROOT variable to your shell's
       environment (that is, define it within your "~/.bashrc" or "~/.chsrc"
@@ -61,9 +73,9 @@
     <h4>Getting Parts of the Source "Tree"</h4>
 
     <p>The above commands demonstrate how to check out all of the MITgcm code
-      and the "contributed" (that is, unsupported by often useful) information
-      within the "MITgcm_contrib" directory.  In many cases, this is overkill
-      and can result in long download times.  To reduce the volume of
+      and the "contributed" (that is, unsupported by occasionally useful)
+      information within the "MITgcm_contrib" directory.  In many cases, this is
+      overkill and can result in long download times.  To reduce the volume of
       information downloaded and thereby speedup the download times, one can
       select one of the following pre-defined "aliases" that will provide a
       sub-set of the entire MITgcm source "tree":</p>
@@ -82,7 +94,7 @@
  	<td width="25%">MITgcm_verif_basic</td>
 	<td>Source code plus a small set of the verification examples
 	  ("global_ocean.90x40x15", "aim.5l_cs", "hs94.128x64x5", 
-	  "front_relax").</td>
+	  "front_relax", and "plume_on_slope").</td>
      </tr>
       <tr bgcolor="#bbffdd">
 	<td width="25%">MITgcm_verif_atmos</td>
@@ -108,11 +120,19 @@
       -->
     </table>
 
+    <p>It is important to note that the CVS aliases above cannot be used in
+      conjunction with the CVS <i>-d DIRNAME</i> option.  However, the MITgcm
+      directories they create can be changed to a different name following the
+      check-out:</p>
+<pre>
+  $ cvs co MITgcm_verif_basic
+  $ mv MITgcm MITgcm_verif_basic
+</pre>
 
     <h4>Getting Specific Releases or "Checkpoints"</h4>
     
     <p>As shown within the <a
-      href="http://dev.mitgcm.org/cgi-bin/viewcvs.cgi/MITgcm/doc/tag-index"> CVS
+      href="http://mitgcm.org/cgi-bin/viewcvs.cgi/MITgcm/doc/tag-index"> CVS
       Code Browser</a>, the MITgcm code is continuously undergoing updates.  At
       points during the development (typically, after work has been done and the
       source code has passed the <a href="testing/latest.html">verification