CVS Client command Line learning notes

Orders are trivial.
CD ~
Environment variable add: ~/.bash_profile

Export cvsroot=:p Server:chenchao@10.4.37.12:/home/cvsroot

SOURCE ~/.bash_profile
MAC Linux Universal Windows is set in path.

The variable is the key.

1. Import a project project: CVS import-m "import init tag" project_name Ver_tag Rel_tag

2. Download a project engineering:

CVS Co project_name

3. Add a file or directory:

CVS Add File/dir

CVS CI file/dir

4. Sync code with CVS server:

CVS up

5. Play tag for the project:

CVS Tag-c release-1-0

6. Export a project project with no CVS directory:

#cvs export-d now PROJECT_NAME//export current version

#cvs export-r release PROJECT_NAME///export the appropriate releases version

7. Branch creation: Create a PROJECT_NAME patch branch under RELEASE_1_0

#cvs Rtag-b-R release_1_0 release_1_0_patch Project_Name

Some people first export Release_1_0_patch this branch in another directory: Solve 1.0 of emergency problems,

CVS Checkout-r Release_1_0_patch

Other people are still developing on the main branch of the project 2.x

After correcting the error on the Release_1_0_patch, mark an error correction version number of 1.0

CVS Tag release_1_0_patch_1

If 2.0 considers these error modifications to be required in 2.0, you can also merge the changes in the release_1_0_patch_1 into the current code in the 2.0 Development directory:

CVS Update-j release_1_0_patch_1

8. View the different versions of the current file for differences:

#cvs diff-r1.3-r1.5 file_name

9. View the difference between the current file (which may have been modified) and the corresponding file in the library:

#cvs diff file_name

10. For upload is not a text file operation: for example:

#cvs add-kb New_file.gif

#cvs add-kb Readme.doc

11. Delete Files:

#cvs rm-f file_name

#cvs ci-m "Why delete file"

12. Environment variable Add: ~/.bash_profile

Export cvsroot=:p Server:chenchao@10.4.37.12:/home/cvsroot