/[MITgcm]/mitgcm.org/front_content/using_cvs.xml
ViewVC logotype

Diff of /mitgcm.org/front_content/using_cvs.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph | View Patch Patch

revision 1.1 by edhill, Thu Dec 4 02:14:52 2003 UTC revision 1.8 by edhill, Tue Jun 29 02:09:47 2004 UTC
# Line 14  Line 14 
14      <meta name="add_title" content="Using CVS" />      <meta name="add_title" content="Using CVS" />
15      <!-- Hinting for menu generation -->      <!-- Hinting for menu generation -->
16    
     <title>MITgcm: <!--ADDTITLE--></title>  
17  <style type="text/css">  <style type="text/css">
18   span.c2 {font-size: 110%}   span.c2 {font-size: 110%}
19   div.c1 {text-align: center}   div.c1 {text-align: center}
# Line 33  Line 32 
32        to use the CVS "pserver" mechanism.  This method only allows you to "check        to use the CVS "pserver" mechanism.  This method only allows you to "check
33        out" (or obtain a local copy) of the source.  It does not provide a        out" (or obtain a local copy) of the source.  It does not provide a
34        mechanism for "committing" or "checking in" changes (please see below).        mechanism for "committing" or "checking in" changes (please see below).
35        Using CVS pserver from the command line requires just a three        Using CVS pserver from the command line requires just a three commands.
36        commands:</p>        Using a Bourne, "bash", or "sh-compatible" shell they are:</p>
37            
 <blockquote>  
 Using a Bourne, "bash", or "sh-compatible" shell:  
38  <pre>  <pre>
39  $  export CVSROOT=':pserver:cvsanon@mitgcm.org:/usr/local/gcmpack'    $ export CVSROOT=':pserver:cvsanon@mitgcm.org:/u/gcmpack'
40  $  cvs login    $ cvs login
41  ( enter the CVS password: "cvsanon" )      ( enter the CVS password: "cvsanon" )
42  $  cvs co MITgcm MITgcm_contrib    $ cvs co MITgcm MITgcm_contrib
 </pre><br />  
   
 Using a "C", "csh", or "tcsh" shell:  
 <pre>  
 $  setenv CVSROOT ':pserver:cvsanon@mitgcm.org:/usr/local/gcmpack'  
 $  cvs login  
 ( enter the CVS password: "cvsanon" )  
 $  cvs co MITgcm MITgcm_contrib  
43  </pre>  </pre>
44  </blockquote>  
45        <p>Using a "C", "csh", or "tcsh" shell the commands are:</p>
46    
47    <pre>
48      $ setenv CVSROOT ':pserver:cvsanon@mitgcm.org:/u/gcmpack'
49      $ cvs login
50        ( enter the CVS password: "cvsanon" )
51      $ cvs co MITgcm MITgcm_contrib
52        </pre>
53    
54      <p>Note that you will only need to perform the "cvs login" once.  And for      <p>Note that you will only need to perform the "cvs login" once.  And for
55        convenience, you may want to add the CVSROOT variable to your shell's        convenience, you may want to add the CVSROOT variable to your shell's
# Line 82  $  cvs co MITgcm MITgcm_contrib Line 79  $  cvs co MITgcm MITgcm_contrib
79        </tr>        </tr>
80        <tr bgcolor="#bbddff">        <tr bgcolor="#bbddff">
81          <td width="25%">MITgcm_verif_basic</td>          <td width="25%">MITgcm_verif_basic</td>
82          <td>Source code plus three of the verification examples          <td>Source code plus a small set of the verification examples
83            ("adjustment.128x64x1", "internal_wave", and            ("global_ocean.90x40x15", "aim.5l_cs", "hs94.128x64x5",
84            "solid-body.cs-32x32x1").</td>            "front_relax", and "plume_on_slope").</td>
85       </tr>       </tr>
86        <tr bgcolor="#bbffdd">        <tr bgcolor="#bbffdd">
87          <td width="25%">MITgcm_verif_atmos</td>          <td width="25%">MITgcm_verif_atmos</td>
# Line 110  $  cvs co MITgcm MITgcm_contrib Line 107  $  cvs co MITgcm MITgcm_contrib
107        -->        -->
108      </table>      </table>
109    
110        <p>It is important to note that the CVS aliases above cannot be used in
111          conjunction with the CVS <i>-d DIRNAME</i> option.  However, the MITgcm
112          directories they create can be changed to a different name following the
113          check-out:</p>
114    <pre>
115      $ cvs co MITgcm_verif_basic
116      $ mv MITgcm MITgcm_verif_basic
117    </pre>
118    
119      <h4>Getting Specific Releases or "Checkpoints"</h4>      <h4>Getting Specific Releases or "Checkpoints"</h4>
120            
121      <p>As shown within the <a      <p>As shown within the <a
122        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
123        Code Browser</a>, the MITgcm code is continuously undergoing updates.  At        Code Browser</a>, the MITgcm code is continuously undergoing updates.  At
124        points during the development (typically, after work has been done and the        points during the development (typically, after work has been done and the
125        source code has passed the <a href="testing/latest.html">verification        source code has passed the <a href="testing/latest.html">verification
# Line 123  $  cvs co MITgcm MITgcm_contrib Line 128  $  cvs co MITgcm MITgcm_contrib
128        development.  One can check out these versions using the "-r TAG_NAME" CVS        development.  One can check out these versions using the "-r TAG_NAME" CVS
129        option such as: </p>        option such as: </p>
130    
 <blockquote>  
131  <pre>  <pre>
132  $  cvs co -r release1_p5 MITgcm    $ cvs co -r release1_p5 MITgcm
133  $  cvs co -r checkpoint52a_post MITgcm    $ cvs co -r checkpoint52a_post MITgcm
134  </pre>  </pre>
 </blockquote>  
135    
136      <p>By default (that is, when no tag is specified), CVS will retrieve the      <p>By default (that is, when no tag is specified), CVS will retrieve the
137        latest version of all files.</p>        latest version of all files.</p>
# Line 140  $  cvs co -r checkpoint52a_post MITgcm Line 143  $  cvs co -r checkpoint52a_post MITgcm
143        that you yourself have made since obtaining the code.  From within        that you yourself have made since obtaining the code.  From within
144        your working directory:</p>        your working directory:</p>
145    
146  <blockquote>  <pre>
147  <pre>cvs diff</pre>    cvs diff
148  </blockquote>  </pre>
149    
150    
151      <p>will show the differences between your version and the version that you      <p>will show the differences between your version and the version that you
152        checked out. It acts recursively on all directories below your current        checked out. It acts recursively on all directories below your current
153        directory. You can limit the operation to just one file or directory by        directory. You can limit the operation to just one file or directory by
154        specifying those as arguments:</p>        specifying those as arguments:</p>
155    
156  <blockquote>  <pre>
157  <pre>cvs diff <i>file</i></pre>    cvs diff <i>file</i>
158  </blockquote>  </pre>
159    
160    
161      <h4>Show changes to the repository that you don't have</h4>      <h4>Show changes to the repository that you don't have</h4>
162    
163      <p>The source code evolves continuously and you should try to stay up to      <p>The source code evolves continuously and you should try to stay up to
164        date.  To see what needs to be updated:</p>        date.  To see what needs to be updated:</p>
165    
166  <blockquote>  <pre>
167  <pre>cvs -n update</pre>    cvs -n update
168  </blockquote>  </pre>
169    
170      <p>behaves just as "cvs update" but doesn't actually change anything. This      <p>behaves just as "cvs update" but doesn't actually change anything. This
171        is a useful way of summarizing the state of your code. The meaning of the        is a useful way of summarizing the state of your code. The meaning of the
# Line 171  $  cvs co -r checkpoint52a_post MITgcm Line 176  $  cvs co -r checkpoint52a_post MITgcm
176      <p>You can download and merge updates from the repository to bring you      <p>You can download and merge updates from the repository to bring you
177        working code up to date:</p>        working code up to date:</p>
178    
179  <blockquote>  <pre>
180  <pre>cvs update -d -P</pre>    cvs update -d -P
181  </blockquote>  </pre>
182    
183        <p>will work recursively on all files in the current directory and below.        <p>will work recursively on all files in the current directory and below.
184          To update just a specific file or directory:</p>          To update just a specific file or directory:</p>
185    
186  <blockquote>  <pre>
187  <pre>cvs update <i>file</i></pre>    cvs update <i>file</i>
188  </blockquote>  </pre>
189    
190      <p>You can also update to a specific version, just as you could check out      <p>You can also update to a specific version, just as you could check out
191        a specific version.</p>        a specific version.</p>
192    
193  <blockquote>  <pre>
194  <pre>cvs update -d -P -r release1_p5</pre>    cvs update -d -P -r release1_p5
195  </blockquote>  </pre>
196    
197      <p>If you checked out a specific version and want to update to the very      <p>If you checked out a specific version and want to update to the very
198        latest use the -A option will remove associated with a specific version as        latest use the -A option will remove associated with a specific version as
199        follows:</p>        follows:</p>
200    
201  <blockquote>  <pre>
202  <pre>cvs update -d -P -A</pre>    cvs update -d -P -A
203  </blockquote>  </pre>
204    
205      <p>"cvs update" produces output to the terminal with the following      <p>"cvs update" produces output to the terminal with the following
206        meanings:</p>        meanings:</p>
Legend:
Removed from v.1.1  
changed lines
  Added in v.1.8
  ViewVC Help
Powered by ViewVC 1.1.22