136 |
|
|
137 |
<h4>Getting Specific Releases or "Checkpoints"</h4> |
<h4>Getting Specific Releases or "Checkpoints"</h4> |
138 |
|
|
139 |
<p>As shown within the <a |
<p>As shown within the |
140 |
href="http://mitgcm.org/cgi-bin/viewcvs.cgi/MITgcm/doc/tag-index"> CVS |
<!-- <a href="http://mitgcm.org/cgi-bin/viewcvs.cgi/MITgcm/doc/tag-index">CVS Code Browser</a> --> |
141 |
Code Browser</a>, the MITgcm code is continuously undergoing updates. At |
<a href="http://mitgcm.org/viewvc/MITgcm/MITgcm/doc/tag-index">CVS Code Browser</a> |
142 |
|
, the MITgcm code is continuously undergoing updates. At |
143 |
points during the development (typically, after work has been done and the |
points during the development (typically, after work has been done and the |
144 |
source code has passed the <a href="testing/latest.html">verification |
source code has passed the <a href="./testing.html">verification |
145 |
tests</a>), a release or checkpoint "tag" is created. These tags are a |
tests</a>), a release or checkpoint "tag" is created. These tags are a |
146 |
convenient mechanism for referring to different times or points within the |
convenient mechanism for referring to different times or points within the |
147 |
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 |