Concurrent Version System

Jaeho Shin <netj@SPARCS>2001/05/14

What’s CVS? Concurrent Version System Can record the history of your source

files Every versions of every files are saved in

an efficient way Asynchronous control

The Repository and the Working Directory Non-exclusive control

Access to one file by multiple developers

The Repository Where all your files are stored CVSROOT environment variable “cvs -d <repository> <command> …” To create a repository

“cvs init” Remote Repository

pserver/kserver/cvsup

The Working Directory Where your works are saved Must use “commit” command to synchro

nize with the repository To create a working directory

“cvs checkout <module>”

Working with CVS① Checkout

“cvs checkout <module>”② Edit

Do something with your checked out files③ Update/Add/Remove

“cvs update <files>” “cvs add <files>” “cvs remove <files>”

④ Commit “cvs commit”

Working with CVS 2 Importing sources

“cvs import <repository> <vendor-tag> <release-tags> …”

Tagging “cvs tag <tag> <filename>”

Exporting sources “cvs export -r <tag> <module> …”

Working with CVS 3 To view the repository access history

“cvs history” To view the log of files

“cvs log <filename> …” To view the status of checked out files

“cvs status <filename> …”

Working with CVS 4 To watch on files

“cvs watch [on|off|add|remove] <files> …” “cvs watchers <filename> …”

To notice you are editing “cvs edit <filename> …” “cvs unedit <filename> …” “cvs editors <filename> …”

References CVS website

http://www.CVShome.org/ Man pages

“man cvs” CVS help messages

“cvs --help” “cvs –help-commands” “cvs –help-options”