From: Brian Date: Tue, 5 Dec 2006 23:27:31 +0000 (-0700) Subject: Removed/obsolete. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=492e406fec1dc6b9d8731ee77ddf0af5cfc0a641;p=mesa.git Removed/obsolete. --- diff --git a/docs/cvs_access.html b/docs/cvs_access.html deleted file mode 100644 index 797bcb693ca..00000000000 --- a/docs/cvs_access.html +++ /dev/null @@ -1,106 +0,0 @@ - - -CVS Access - - - - - -

CVS Access

- -

-Mesa's CVS repository (code management system) is hosted on -freedesktop.org. -

- -

-You may access the repository either as an -anonymous user (read-only) or as a -developer -(read/write). -

- -

-You may also -browse the CVS repository. -

- - - -

Anonymous CVS Access

- -

-Anonymous, public, read-only access to the CVS repository is available. -Here are the basic instructions for Unix systems: -

- -

Install CVS client software on your computer if needed. - Version 1.9.28 is known to work. -
Login as an anonymous user: -
```
-    cvs -d:pserver:anonymous@anoncvs.freedesktop.org:/cvs/mesa login
-    
```
- Just press Enter/Return when prompted for a password. -
-
-

Check out the code: -

-    cvs -d:pserver:anonymous@anoncvs.freedesktop.org:/cvs/mesa co Mesa
-

- - -

To update your Mesa CVS source to the latest CVS source:

- -

cd Mesa -
cvs -z3 -d:pserver:anonymous@anoncvs.freedesktop.org:/cvs/mesa update -

- - - -

Developer CVS Access

- -

-Mesa developers working with the Mesa CVS repository need to first -have an account on -freedesktop.org. -To get an account, please ask Brian or the other Mesa developers for -permission. -Then, if there are no objections, follow this - -procedure. -

- -

-Once your account is established, you can check out the Mesa CVS tree -with: -

-   setenv CVS_RSH ssh        (if using a csh-like shell)
-

-OR -

-   export CVS_RSH=rsh        (if using a bash-like shell)
-

-followed by: -

-   cvs -d:ext:yourusername@cvs.freedesktop.org:/cvs/mesa co Mesa
-

- -

-Of course, replace yourusername with your actual login name. -

- -

-Subsequent updates should only require: -

-   cvs update
-

- - - - - diff --git a/docs/cvs_branches.html b/docs/cvs_branches.html deleted file mode 100644 index 98df3d0f4f7..00000000000 --- a/docs/cvs_branches.html +++ /dev/null @@ -1,80 +0,0 @@ - - -CVS Branches - - - - - -

CVS Branch Information

- -

-At any given time, there may be several active branches in Mesa's -CVS repository. - -Generally, the CVS trunk contains the latest development (unstable) -code while a CVS branch has the latest stable 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. -

- -

-Mesa releases use an even/odd numbering scheme to represent stable/development -releases. - -For example, Mesa 6.2 (0 is considered even) is a stable release while -Mesa 6.3 is a development release. -

- -

-To checkout a specific CVS branch pass -r and -the branch tag after your CVS command. - -For example cvs checkout -r mesa_6_2_branch Mesa will -checkout the 6.2 branch and cvs update -r -mesa_6_2_branch will convert your current CVS tree to the 6.2 -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 branches 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
-

- -

-Most will be obsolete branches. Generally, the newer branches are at -the top. Ask on the mesa3d-dev mailing list to learn which branches -are active. -

- - - - \ No newline at end of file