The Mesa3d sources are split up into two branches. A branch that is to
remain as stable as possible, and an unstable branch where development
work for new versions will be done. The current stable branch is
tagged mesa_3_4_branch while the unstable branch is just
the default. The goal is to adopt and even/odd stable/unstable
versioning scheme similar to the Linux kernel. Hence releases of Mesa
3.2.X should be more stable than Mesa 3.3.X.
All versions of
Mesa after 3.0 will also be tagged with a branch id. Mesa 3.1 has the
tag mesa_3_1, Mesa 3.2 will be mesa_3_2,
Mesa 3.3 mesa_3_3, etc..
To checkout a specific branch of mesa just pass -r and
the branch tag after your cvs command. For example cvs checkout
-r mesa_3_4_branch Mesa will checkout the 3.4 branch and
cvs update -r mesa_3_4_branch will convert your current
branch to the 3.4 dev branch.
Consult http://www.durak.org/cvswebsites/doc/cvs_5.php3#SEC54
for more on branching in cvs.
To see a list of all the CVS branchs run cvs log README (or any
other file) and look for the section labeled symbolic names.
You'll see something like this:
symbolic names:
mesa_4_0: 1.3
mesa_4_0_branch: 1.3.0.6
mesa_3_5: 1.3
mesa_3_4_2: 1.3
mesa_3_4_1: 1.3
mesa_3_4: 1.3
mesa_3_4_branch: 1.3.0.4
mesa_3_3: 1.3
mesa_3_2_1: 1.1.1.1
mesa_3_3_texture_env_combine2: 1.3.0.2
mesa_3_2: 1.1.1.1
mesa_3_2_beta_1: 1.1.1.1
mesa_3_1: 1.1.1.1
mesa_3_2_dev: 1.1.1.1.0.2
mesa_3_1_beta_3: 1.1.1.1
start: 1.1.1.1
mesa: 1.1.1