• QUICK LINKS
  • answers.stanford.edu
  • apple.stanford.edu
  • computing.stanford.edu
  • courses.stanford.edu
  • datarates.stanford.edu
  • dell.stanford.edu
  • departmentphone.stanford.edu
  • email.stanford.edu
  • ess.stanford.edu
  • helpsu.stanford.edu
  • myitserviceshelp.stanford.edu
  • orderithelp.stanford.edu
  • software.stanford.edu
  • studentphone.stanford.edu
  • techtraining.stanford.edu
  • tools.stanford.edu
  • unixcomputing.stanford.edu
  • vpn.stanford.edu
  • web.stanford.edu
  • windows.stanford.edu
• SERVICES
  • IT Services Only
  • All Campus Providers
    → computing.stanford.edu
• GETTING HELP
  • Stanford Answers
  • HelpSU: IT Help Desk
  • Training
• PROJECTS
• ABOUT US
  • What We Do
  • Organization Chart
  • Strategic Plan
  • Jobs
  • Contact info
  • Service & System Metrics
• INTERNAL
• SEARCH

  • Search IT Services:
     

• Pubsw Software
• Index of Leland Software
• CVS 1.12.13

CVS 1.12.13

Summary

Description: Concurrent version control system
Source: http://www.cvshome.org/

Support

This package is available for all platforms. This package is unsupported and provided on an as-is basis.

Description

CVS (Concurrent Versioning System) is a version control system, which allows you to keep old versions of files (usually source code), keep a log of who, when, and why changes occurred, etc., like RCS or SCCS. Unlike the simpler systems, CVS does not just operate on one file at a time or one directory at a time, but operates on hierarchical collections of directories consisting of version controlled files. CVS helps to manage releases and to control the concurrent editing of source files among multiple authors. CVS allows triggers to enable/log/control various operations and works well over a wide area network.

CVS keeps a single copy of the master sources. This copy is called the source "repository"; it contains all the information to permit extracting previous software releases at any time based on either a symbolic revision tag, or a date in the past.

Changes

1.12.13 2005-10-03

Require new version of Zlib compression libraries in order to avoid a security vulnerability. Sections of directives specific to one or more repositories and not others may now be specified in the config file. Missing CVSROOT/history files will now cause CVS to attempt to create one. To suppress history logging, set LogHistory equal to the empty string in CVSROOT/config. There are several new options available in CVSROOT/config. These are TmpDir, HistoryLogPath, HistorySearchPath, MinCompressionLevel, & MaxCompressionLevel.

1.11.6 2003-09-17

Improved error handling and improvements to the build system. For the complete changes, see /usr/pubsw/doc/Development/cvs/NEWS.

1.11.5 2003-03-26

Fixed a security vulnerability in pserver.

1.11.4 2003-01-27

Internal bug and build system fixes, and show lock times in UTC rather than in the local time of the server.

1.11.2 2002-07-16

Added options to log and rlog to suppress header information when no revisions are selected, moving and deleting branch tags requires an extra option to avoid accidents, and annotate no longer annotates binary files without -F.

1.11.1p1 2002-01-05

New commands to retrieve log and annotation information without having a checked-out copy, a new format for the .cvspass file, and password and port numbers supported in the CVSROOT string.

Files

   Programs: cvs cvsbug
Other Files: /usr/pubsw/lib/cvs
  Man Pages: cvs(1) cvs(5) cvsbug(8)
 Info Pages: cvs cvsclient

Accuracy

This information reflects the version of this package that is installed in Stanford's site-wide pubsw software tree. Newer versions of the package may be available from the package source. The contents of this page, including the source URL if applicable, are generally only reviewed when the package is upgraded and therefore may not accurately reflect the current version of the package.