3 Copyright (c) 1993-1994 Brian Berliner
4 Copyright (c) 1992 Brian Berliner and Jeff Polk
5 Copyright (c) 1989-1992, Brian Berliner
8 This program is free software; you can redistribute it and/or modify
9 it under the terms of the GNU General Public License as published by
10 the Free Software Foundation; either version 1, or (at your option)
13 This program is distributed in the hope that it will be useful,
14 but WITHOUT ANY WARRANTY; without even the implied warranty of
15 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16 GNU General Public License for more details.
18 -------------------------------------------------------------------------------
22 If you have problems or think you have found a bug in CVS, see the
23 section BUGS in the CVS manual (also known as Version Management with
24 CVS by Per Cederqvist et al, or cvs.texinfo--see below for details).
26 If you are thinking of submitting changes to CVS, see the
29 Please consult the INSTALL file for information on tested
30 configurations. If you have a comment about an already tested
31 configuration, or have tried CVS on a new configuration, please let us
32 know as described in INSTALL. Free software only works if we all help
35 Finally, we cannot guarantee that this release will not completely wipe out
36 all of your work from your system. We do some simple testing before each
37 release, but you are completely on your own. We recommend testing this
38 release on a source repository that is not critical to your work. THIS
39 SOFTWARE IS SUPPLIED COMPLETELY "AS IS". NO WARRANTY....
41 Thanks for your support!
45 -------------------------------------------------------------------------------
49 CVS is a version control system, which allows you to keep old versions
50 of files (usually source code), keep a log of who, when, and why
51 changes occurred, etc., like RCS or SCCS. It handles multiple
52 developers, multiple directories, triggers to enable/log/control
53 various operations, and can work over a wide area network. The
54 following tasks are not included; they can be done in conjunction with
55 CVS but will tend to require some script-writing and software other
56 than CVS: bug-tracking, build management (that is, make and make-like
57 tools), and automated testing.
59 And a whole lot more. See the manual for more information.
61 -------------------------------------------------------------------------------
63 Notes to people upgrading from a previous release of CVS:
65 See the NEWS file for a description of features new in this version.
67 See the Compatibility section of the manual for information on
68 compatibility between CVS versions. The quick summary is that as long
69 as you not using the optional watch features, there are no
70 compatibility problems with CVS 1.5 or later.
72 -------------------------------------------------------------------------------
76 Please read the INSTALL file for installation instructions. Brief summary:
78 $ ./noautomake.sh --noautoconf
81 (run the regression tests if desired)
83 (create a repository if you don't already have one)
85 The documentation is in the doc subdirectory. cvs.texinfo is the main
86 manual; cvs.info* and cvs.ps are the info and postscript versions,
87 respectively, generated from cvs.texinfo. The postscript version is
88 for US letter size paper; we do this not because we consider this size
89 "better" than A4, but because we believe that the US letter version
90 will print better on A4 paper than the other way around. If you want a
91 version formatted for A4, add the line @afourpaper near the start of
92 cvs.texinfo and re-generate cvs.ps using TeX.
94 -------------------------------------------------------------------------------
96 * How do I get up-to-date information and information about other
99 On the web, http://www.loria.fr/~molli/cvs-index.html.
102 http://www.cvshome.org
104 The mailing list for CVS is info-cvs@gnu.org. Send
105 subscription and removal requests for that list to
106 info-cvs-request@gnu.org.
108 The newsgroup for CVS (and other configuration management systems) is
109 comp.software.config-mgmt. There is not yet a CVS-specific newsgroup,
110 but perhaps if comp.software.config-mgmt gets enough CVS discussion,
111 then it will be possible to create one.
113 -------------------------------------------------------------------------------
117 The conflict-resolution algorithms and much of the administrative file
118 definitions of CVS were based on the original package written by Dick Grune
119 at Vrije Universiteit in Amsterdam <dick@cs.vu.nl>, and posted to
120 comp.sources.unix in the volume 6 release sometime in 1986. This original
121 version was a collection of shell scripts. I am thankful that Dick made
124 Brian Berliner from Prisma, Inc. (now at Sun Microsystems, Inc.)
125 <berliner@sun.com> converted the original CVS shell scripts into reasonably
126 fast C and added many, many features to support software release control
127 functions. See the manual page in the "man" directory. A copy of the
128 USENIX article presented at the Winter 1990 USENIX Conference, Washington
129 D.C., is included in the "doc" directory.
131 Jeff Polk from BSDI <polk@bsdi.com> converted the CVS 1.2
132 sources into much more readable and maintainable C code. He also added a
133 whole lot of functionality and modularity to the code in the process.
134 See the bottom of the NEWS file (from about 1992).
136 david d `zoo' zuhn <zoo@armadillo.com> contributed the working base code
137 for CVS 1.4 Alpha. His work carries on from work done by K. Richard Pixley
138 and others at Cygnus Support. The CVS 1.4 upgrade is due in large part to
141 David G. Grubbs <dgg@odi.com> contributed the CVS "history" and "release"
142 commands. As well as the ever-so-useful "-n" option of CVS which tells CVS
143 to show what it would do, without actually doing it. He also contributed
144 support for the .cvsignore file.
146 The Free Software Foundation (GNU) contributed most of the portability
147 framework that CVS now uses. This can be found in the "configure" script,
148 the Makefile's, and basically most of the "lib" directory.
150 K. Richard Pixley, Cygnus Support <rich@cygnus.com> contributed many bug
151 fixes/enhancement as well as completing early reviews of the CVS 1.3 manual
154 Roland Pesch, then of Cygnus Support <roland@wrs.com> contributed
155 brand new cvs(1) and cvs(5) manual pages. Thanks to him for saving us
156 from poor use of our language!
158 Paul Sander, HaL Computer Systems, Inc. <paul@hal.com> wrote and
159 contributed the code in lib/sighandle.c. I added support for POSIX, BSD,
160 and non-POSIX/non-BSD systems.
162 Jim Kingdon and others at Cygnus Support <info@cygnus.com> wrote the
163 remote repository access code.
165 There have been many, many contributions not listed here. Consult the
166 ChangeLog files in each directory for a more complete idea.
168 In addition to the above contributors, the following Beta testers
169 deserve special mention for their support. This is only a partial
170 list; if you have helped in this way and would like to be listed, let
171 bug-cvs know (as described in the Cederqvist manual).
173 Mark D. Baushke <mdb@cisco.com>
174 Per Cederqvist <ceder@signum.se>
175 J.T. Conklin <jtc@cygnus.com>
176 Vince DeMarco <vdemarco@fdcsrvr.cs.mci.com>
177 Paul Eggert <eggert@twinsun.com>
178 Lal George <george@research.att.com>
179 Dean E. Hardi <Dean.E.Hardi@ccmail.jpl.nasa.gov>
180 Mike Heath <mike@pencom.com>
181 Jim Kingdon <kingdon@cygnus.com>
182 Bernd Leibing <bernd.leibing@rz.uni-ulm.de>
183 Benedict Lofstedt <benedict@tusc.com.au>
184 Dave Love <d.love@dl.ac.uk>
185 Robert Lupton the Good <rhl@astro.princeton.edu>
186 Tom McAliney <tom@hilco.com>
187 Eberhard Mattes <mattes@azu.informatik.uni-stuttgart.de>
188 Jim Meyering <meyering@comco.com>
189 Thomas Mohr <mohr@lts.sel.alcatel.de>
190 Thomas Nilsson <thoni@softlab.se>
191 Raye Raskin <raye.raskin@lia.com>
192 Harlan Stenn <harlan@landmark.com>
193 Gunnar Tornblom <gunnar.tornblom@senet.abb.se>
194 Greg A. Woods <woods@planix.com>
196 Many contributors have added code to the "contrib" directory. See the
197 README file there for a list of what is available. There is also a
198 contributed GNU Emacs CVS-mode in tools/pcl-cvs.