O'Reilly Network: Introduction to CVS

"This is the first in a two-part series on CVS. This article is intended for folks who will be using CVS already installed on a system. In it, the author explains check-out, update, adding, merging, and other functions. In the second part, scheduled to run later this month, she will show how to create and manage a CVS repository, for those who need to start from scratch. -- Ed.

CVS -- or Concurrent Versioning System -- is a system for managing simultaneous development of files. It is in common use in large programming projects, and is also useful to system administrators, technical writers, and anyone who needs to manage files.

CVS stores files in a central repository, set (using standard Unix permissions) to be accessible to all users of the files. Commands are given to "check out" a copy of a file for development, and "commit" changes back to the repository. It also scans the files as they are moved to and from the repository, to prevent one person's work from overwriting another's."

Complete Story

Related Stories:

• Advogato: CVS mixed-tagging for massive Open Source Project Management(Feb 21, 2001)
• CVSSearch: A New Way to Search through Code(Feb 04, 2001)
• zez.org: Version Control management with CVS - Part 2(Nov 26, 2000)
• zez.org: Version Control Management with CVS - Part 1(Nov 07, 2000)
• CVS 1.11 Released; New URL for Home Page(Oct 04, 2000)
• LinuxPR: Little Book Packs a Lot of Info on CVS (Aug 24, 2000)
• LinuxPlanet: Using the Apache CVS Repository(Apr 14, 2000)
• SunWorld: CVS in the scripting landscape(Oct 03, 1999)
• The CVS Continuity Project(Jul 06, 1999)