summaryrefslogtreecommitdiff
path: root/docs/cvs_branches.html
diff options
context:
space:
mode:
authorBrian Paul <brian.paul@tungstengraphics.com>2004-10-02 15:26:25 +0000
committerBrian Paul <brian.paul@tungstengraphics.com>2004-10-02 15:26:25 +0000
commit7e73b1afa2de1989251aee4ad2d609ff141f4a5e (patch)
tree982409de1a8f07f2ef2af7f5615a474ba188fa70 /docs/cvs_branches.html
parent9ca83924848070d02a5ac2f0aa4e20444eec2183 (diff)
a few more updates for the 6.2 release
Diffstat (limited to 'docs/cvs_branches.html')
-rw-r--r--docs/cvs_branches.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/cvs_branches.html b/docs/cvs_branches.html
index 5f653b7830..cc07c58ae4 100644
--- a/docs/cvs_branches.html
+++ b/docs/cvs_branches.html
@@ -15,25 +15,25 @@ code while a CVS branch has the latest stable code.
</p>
<p>
-Currently (Nov 2003), the trunk is the Mesa 5.1 development code
-while the mesa_5_0_branch branch has the stable Mesa 5.0.x code.
+Currently (Oct 2004), the trunk is the Mesa 6.3 development code
+while the mesa_6_2_branch branch has the stable Mesa 6.2.x code.
</p>
<p>
Mesa releases use an even/odd numbering scheme to represent stable/development
releases.
-For example, Mesa 5.0.x (0 is considered even) is a stable release while
-Mesa 5.1.x is a development release.
+For example, Mesa 6.2 (0 is considered even) is a stable release while
+Mesa 6.3 is a development release.
</p>
<p>
To checkout a specific CVS branch pass <code>-r</code> and
the branch tag after your CVS command.
-For example <code>cvs checkout -r mesa_5_0_branch Mesa</code> will
-checkout the 5.0.x branch and <code>cvs update -r
-mesa_5_0_branch</code> will convert your current CVS tree to the 5.0.x
+For example <code>cvs checkout -r mesa_6_2_branch Mesa</code> will
+checkout the 6.2 branch and <code>cvs update -r
+mesa_6_2_branch</code> will convert your current CVS tree to the 6.2
branch.
Consult <a href="http://www.durak.org/cvswebsites/doc/cvs_5.php3#SEC54"