6 * Thanks to a report from Alen Zukich <alen.zukich@klocwork.com>, several minor
7 security issues have been addressed. One was a buffer overflow that is
8 potentially serious but which may not be exploitable, assigned CAN-2005-0753
9 by the Common Vulnerabilities and Exposures Project
10 <http://www.cve.mitre.org>. Other fixes resulting from Alen's report include
11 repair of an arbitrary free with no known exploit and several plugged memory
12 leaks and potentially freed NULL pointers which may have been exploitable for
13 a denial of service attack.
15 * Thanks to a report from Craig Monson <craig@malachiarts.com>, minor
16 potential vulnerabilities in the contributed Perl scripts have been fixed.
17 The confirmed vulnerability could allow the execution of arbitrary code on
18 the CVS server, but only if a user already had commit access and if one of
19 the contrib scripts was installed improperly, a condition which should have
20 been quickly visible to any administrator. The complete description of the
21 problem is here: <https://ccvs.cvshome.org/issues/show_bug.cgi?id=224>. If
22 you were making use of any of the contributed trigger scripts on a CVS
23 server, you should probably still replace them with the new versions, to be
26 Unfortunately, our fix is incomplete. Taint-checking has been enabled in all
27 the contributed Perl scripts intended to be run as trigger scripts, but no
28 attempt has been made to ensure that they still run in taint mode. You will
29 most likely have to tweak the scripts in some way to make them run. Please
30 send any patches you find necessary back to <bug-cvs@gnu.org> so that we may
31 again ship fully enabled scripts in the future.
33 You should also make sure that any home-grown Perl scripts that you might
34 have installed as CVS triggers also have taint-checking enabled. This can be
35 done by adding `-T' on the scripts' #! lines. Please try running
36 `perldoc perlsec' if you would like more information on general Perl security
41 * Thanks to a report from Ian Abbott <abbotti@mev.co.uk>, a problem that caused
42 CVS to stop with broken assertions in certain time zones when daylight
43 savings is in effect has been fixed.
45 * A problem where a proxy server could fail to notice that its primary closed
46 the connection has been fixed.
48 * Failures to open the CVS_CLIENT_LOG, CVS_SERVER_LOG, and CVS_SECONDARY_LOG
51 * CVS's client and server IO buffers now rely on a GNULIB modules for memory
52 management rather than taking on the task themseleves. This should be faster
53 on any system but may increase memory usage noticably on systems without the
54 POSIX mmap() function. Benchmark reports to <bug-cvs@gnulib.org> would be
57 * Some more GNULIB functions have been imported and/or updated for portability
58 reasons. This change should not be visible to most users, though CVS may now
59 compile on a few more platforms.
61 * CVS creates a unique session id that gets written to the RCS files during
62 import and commit. When committing several files at once, they all get the
63 same 'commitid'. The commitid becomes visible with log and status commands,
64 and is derived and compatible with the cvsnt project.
66 * CVS once again compiles correctly configured with various combinations of
67 --disable-client, --disable-server, and --disable-proxy.
69 * CVS now accepts the <tag>:<date> format, which has long been acceptable as an
70 argument to -j options, in most places where <tag> used to be acceptable. An
71 empty tag in this format (e.g. ":<date>"), which used to be rejected, is now
72 interpreted as specifying a date on the trunk.
74 * CVS now uses ZLib 1.2.2. This fixes the minor vulnerability described here:
75 <http://www.kb.cert.org/vuls/id/238678>, as well as some other minor bugs we
76 are not aware of bug reports for in conjunction with CVS.
78 * `cvs -n release' now does what it should (see changes to the info-cleanup-0
79 test in sanity.sh for more).
81 * The configure script now prefers `ssh' to `rsh' when determining a default
82 executable to use when connecting via the :ext: method.
84 * A problem in the compression buffer that was causing some incompatibility
85 with some 3rd party CVS clients when compression was enabled has been fixed.
87 * Some files missing from the distribution have been added or readded. The
88 missing files were mostly development support files, with a few docs and
89 .cvsignore files thrown in.
91 * The incomplete Brazillian Portugese translation of the CVS manual is now
92 included in the distribution.
96 * Misc bug and documentation fixes.
98 * CVS now detects write errors on standard output. Before, e.g.,
99 `cvs update -p FILE > /dev/full' would fail to report the write error.
101 * Thanks to a report and a patch from Georg Scwharz <georg.scwarz@freenet.de>
102 CVS now builds without error on IRIX 5.3
106 * We've standardized on Automake 1.9.5 to get some at new features that make
107 our jobs easier. See the HACKING file for more on using the autotools with
110 Changes from 1.12.10 to 1.12.11:
111 ********************************
115 * Thanks to Conrad Pino <conrad@pino.com>, the Windows build works once again.
117 * CVSROOT methods and option names are now case insensitive
119 * CVSROOT methods :ext: and :fork: now support the CVS_SERVER option.
121 * CVSROOT method :ext: now supports the CVS_RSH and Redirect options.
123 * Date handling has been improved slightly.
125 * Miscellaneous bug fixes.
127 * Miscellaneous documentation fixes.
131 * An intermittant assertion failure in checkout has been fixed.
133 * Thanks to a report from Chris Bohn <cbohn@rrinc.com>, all the source files
134 needed to build on Windows are now included in the source distribution.
136 Changes from 1.12.9 to 1.12.10:
137 *******************************
141 * The date formats which CVS accepts are now documented more fully in the
144 * CVS commands which accept dates now understand some more time zones,
145 including those which are some hours plus some fraction of an hour off of
146 universal coordinated time.
148 * `cvs ls filename' no longer causes an assertion failure.
150 * The maximum length of the discovered comment leader used in a Log keyword
151 substitution is now limited to 20 characters by default. If a longer leader
152 is discovered, then the keyword is not expanded. This default behavior may
153 be altered using the new MaxCommentLeaderLength & UseArchiveCommentLeader
156 * Commit messages once again include the full relative path to the file being
159 * Thanks to funding from Juniper Networks <http://juniper.net>, "write proxy"
160 functionality has been added to the CVS server. Write proxy functionality
161 allows any of multiple, read-only "secondary" servers to relay write requests
162 from clients to a single primary CVS server, allowing for a massive
163 redistribution of server load which is transparent to all known CVS clients.
165 * Thanks to funding from Juniper Networks <http://juniper.net>, some code has
166 been added which second-guesses the system file cache for a performance
169 * The loginfo scripting hook now runs after the administrative files in CVSROOT
170 are rebuilt, rather than before.
172 * Misc error message improvements.
174 * Thanks to funding from Juniper Networks <http://juniper.net>, new scripting
175 hooks have been added to the CVS server. These are the postadmin, posttag,
176 and postwatch hooks. See the manual for more info.
178 * Thanks to funding from Juniper Networks <http://juniper.net>, all the
179 existing scripting hooks may now optionally be passed a command name
182 * Thanks to funding from Juniper Networks <http://juniper.net>, new tags are
183 cached in the val-tags file at the time of tag creation.
185 * Thanks to a patch from Brian Murphy <brian@murphy.dk>, CVS now supports PAM
188 * Thanks to a report from Brian Murphy <brian@murphy.dk>, the demo PAM
189 configuration files mentioned in the manual are actually being distributed.
191 * Thanks again to Bart Robinson <lomew@pobox.com>, `cvs log' & `cvs ls' now
192 actually output local times when the server is version 1.12.9 or greater and
193 the client is version 1.12.10 or greater.
195 * The CVS server now sends paths to files relative to the repository. CVS
196 clients have been able to handle this since at least the 10 year old
197 CVS 1.9.2 release, so no attempt at verifying compatibility of clients has
198 been made. This saves a small amount of bandwidth and may enable some future
201 * The CVS client will send relative Directory requests if the server claims to
202 support it. This saves a very small amount of bandwidth but may enable some
203 future functionality.
205 * "cvs import" now has a new option, `-X', which causes new files to be
206 imported in a way that they appear only on the vendor branch, and do not
207 automatically appear on the main trunk.
209 This option may be made the default on a repository-wide basis
210 using the new ImportNewFilesToVendorBranchOnly=yes option in
213 * contrib/cvs_acls.in has been revised. Users of the old version will
214 want to upgrade to use the new format. See the documentation in
215 contrib/cvs_acls.html for more information.
217 * Thanks to Dan Peterson <dbpete@aol.com>, the contrib/validate_repo script now
218 accepts and logs corrupted revision numbers in RCS archives.
222 * Thanks to a report from Gottfried Ganssauge <gotti@cvshome.org>, CVS no
223 longer exits when it encounters links pointing to paths containing more
226 * Thanks to a report from Dan Peterson <dbpete@aol.com>, error messages from
227 GSSAPI servers are no longer truncated.
229 * Thanks to a report from Dan Peterson <dbpete@aol.com>, attempts to resurrect
230 a file on the trunk that was added on a branch no longer causes an assertion
233 * Thanks to a report from Dan Peterson <dbpete@aol.com>, imports to branches
234 like "1.1." no longer create corrupt RCS archives.
236 * Thanks to a report from Chris Bohn <cbohn@rrinc.com>, links from J.C. Hamlin
237 <jchamlin@ibsys.com>, and code posted by Jonathan Gilligan, we think we have
238 finally corrected the Windows "red-file" (daylight savings time) bug once and
241 * Thanks to a patch from Jeroen Ruigrok/asmodai <asmodai@wxs.nl>, the
242 log_accum.pl script should no longer elicit warnings from Perl 5.8.5.
244 * The r* commands (rlog, rls, etc.) can once again handle requests to run
245 against the entire repository (e.g. `cvs rlog .'). Thanks go to Dan Peterson
246 <dbpete@aol.com> for the report.
248 * A problem where the attempted access of files via tags beginning with spaces
249 could cause the CVS server to hang has been fixed. This was a particular
250 problem with WinCVS clients because users would sometimes accidentally
251 include spaces in tags pasted into a dialog box. This fix also altered some
252 of the error messages generated by the use of invalid tags. Thanks go to Dan
253 Peterson <dbpete@aol.com> for the report.
255 * Thanks to James E Wilson <wilson@specifixinc.com> for a bug fix to
256 modules processing "gcc-core -a !gcc/f gcc" will no longer exclude
257 gcc/fortran by mistake.
259 * Thanks to Conrad Pino <conrad@pino.com>, the Windows build works once again.
261 * Misc updates to the manual.
265 * We've standardized on Automake 1.9.3 to get some at new features that make
266 our jobs easier. See the note below on the Autoconf upgrade for more
269 * We've standardized on Autoconf version 2.59 to get presumed bug fixes and
270 features, but nothing specific. Mostly, once we decide to upgrade one of the
271 autotools we just figure it'll save time later to grab the most current
272 versions of the others too. See the HACKING file for more on using the
275 Changes from 1.12.8 to 1.12.9:
276 ******************************
278 SERVER SECURITY FIXES
280 * Thanks to Stefan Esser & Sebastian Krahmer, several potential security
281 problems have been fixed. The ones which were considered dangerous enough
282 to catalogue were assigned issue numbers CAN-2004-0416, CAN-2004-0417, &
283 CAN-2004-0418 by the Common Vulnerabilities and Exposures Project. Please
284 see <http://www.cve.mitre.org> for more information.
286 * A potential buffer overflow vulnerability in the server has been fixed.
287 This addresses the Common Vulnerabilities and Exposures Project's issue
288 #CAN-2004-0414. Please see <http://www.cve.mitre.org> for more information.
292 * `cvs log' & `cvs ls' now output local times when both the server and client
293 are 1.12.9 or greater. (Thanks to Bart Robinson <lomew@pobox.com>.)
297 * The windows-NT/config.h.in file is now generated dynamically from the
298 root config.h.in file and a few inputs in the windows-NT directory in hopes
299 of keeping it more in sync with the root config.h.in file.
301 Changes from 1.12.7 to 1.12.8:
302 ******************************
304 SERVER SECURITY FIXES
306 * A potential buffer overflow vulnerability in the server has been fixed.
307 Prior to this patch, a malicious client could potentially use carefully
308 crafted server requests to run arbitrary programs on the CVS server machine.
309 This addresses the Common Vulnerabilities and Exposures Project's issue
310 #CAN-2004-0396. Please see <http://www.cve.mitre.org> for more information.
314 * Some redundant output generated by the `cvs commit' command has been removed.
316 * Most output from the `cvs commit' command is suppressed when the -Q global
319 * Repository directory browsing via `cvs rls' & `cvs ls' commands. Expect
320 changes in the long format output soon. The "entries" format output should
321 remain fairly stable for automated parsers.
323 * Glob matches, as specified in ignore lists and wrapper options, now conform
324 to the POSIX.2 specification for fnmatch on all platforms.
326 * The Windows MS Visual C++ project files, including the nmake build files,
327 are now generated with MSVC++ 6.0, but should still work with MSVC++ 5.0.
331 * The cvs.1 man page is now generated automatically from a section of the CVS
334 * Thanks to a report from Mark Andrews at the Internet Systems Consortium, the
335 :ext: connection method no longer relies on a transparent transport that uses
336 an argument processor that can handle arbitrary ordering of options and other
337 arguments when using a username other than the caller's.
339 * Thanks to Ken Raeburn at MIT, directory deletion, whether via `cvs release'
340 or empty directory pruning, now works on network shares under Windows XP.
342 Changes from 1.12.6 to 1.12.7:
343 ******************************
345 SERVER SECURITY ISSUES
347 * Piped checkouts of paths above $CVSROOT no longer work. Previously, clients
348 could have requested the contents of RCS archive files anywhere on a CVS
349 server. This addresses CVE issue CAN-2004-0405. Please see
350 <http://www.cve.mitre.org> for more information.
352 CLIENT SECURITY ISSUES
354 * Clients now check paths from the server to verify that they are within one of
355 the sandboxes the user requested be updated. Previously, a trojan server
356 could have written or overwritten files anywhere the user had access,
357 presenting a serious security risk. This addresses CVE issue CAN-2004-1080.
358 Please see <http://www.cve.mitre.org> for more information.
362 * Imported the most recent version of regex from GNULIB, which actually means
363 some systems will use now their native regex functions instead of compiling
364 CVS's. Users should notice no changes in CVS responses to regular
365 expressions. If you do, please report them to <bug-cvs@gnu.org>.
367 * CVS now accepts the location of HTTP tunnel web proxies as part of the
368 CVSROOT string. Actually using a proxy remains untested. Please report
369 problems and successes to <bug-cvs@gnu.org>.
371 * Configure no longer checks the $TMPDIR, $TMP, & $TEMP variables to set the
372 default temporary directory.
374 * CVS on Cygwin correctly handles X:\ style paths.
376 * Import now uses backslash rather than slash on Windows when checking for
377 "CVS" directories to ignore in import commands.
379 * Relative paths containing up-references (`..') should now work in
380 client/server mode (client fix).
382 * A race condition between the ordering of messages from CVS and messages from
383 called scripts in client/server mode has been removed (server fix).
385 * The check_cvs and cvscheck scripts in the contrib directory have been renamed
386 validate_repo and sandbox_status, respectively, in the interests of clarity.
388 * The Windows MS Visual C++ 6.0 project files have been brought up to date.
389 The nmake build files were regenerated from these files with MSVC++ 5.0.
391 * A memory allocation bug on Windows that could cause at least executions of
392 `cvs status' to fail has been fixed (client fix).
394 * Resurrected files now get their modes and timestamps set correctly and a
395 longstanding bug involving resurrection of an uncommitted removal has been
398 * Some resurrection (cvs add) status messages have changed slightly.
400 * `cvs release' now works with Kerberos or GSSAPI encryption enabled (server
403 * File resurrection from a previously existing revision no longer just reports
404 that it works (server fix).
406 * Misc error & status message corrections.
408 * Diffing of locally added files against arbitrary revisions in an RCS archive
409 is now allowed when a file of the same name exists or used to exist on some
412 * Some user messages have been updated for consistency and spelling.
416 * The message source differentiation in the test suite between client and
417 server executables has been repaired.
419 Changes from 1.12.5 to 1.12.6:
420 ******************************
424 * CVSROOT/*info scripts may not work as expected with executables compiled
425 using VC++ under Windows since all quoting is currently done according to
426 Bourne Shell rules, which probably don't look like command.com rules.
427 Patches gratefully accepted.
429 * Imports will now always ignore directories and files named `CVS' to avoid
430 violating assumptions made by other parts of CVS.
432 * Directories specified to `checkout -d' are no longer required to exist. This
433 consolidates some behavior between `-d' options specified in the modules file
434 and `checkout -d' as well as removing some prior differences between local
435 and client/server mode operation.
437 * A problem with `cvs release' of subdirs that could corrupt CVS/Entries files
438 has been fixed (client/server).
440 * The CVS server's protocol check for unused data from the client is no longer
441 called automatically at program exit in order to avoid potential recursive
442 calls to error when the first close is due to memory allocation or similar
443 problems that cause calls to error() to fail. The check is still made when
444 the server program exits normally.
446 * The CVSROOT/*info files want a new command format and the old style strings
447 have been deprecated. Please see the manual for more information on the new
450 * The spec file has been updated to work with more recent versions of RPM.
452 * Some more GNULIB functions have been imported and/or updated for portability
455 * Several memory leaks have been plugged.
457 * A seg fault which always occurred after waiting on another process's lock
458 in order to establish a promotable lock is now avoided.
460 * An unlikely potential segfault when using the :fork: connection method has
463 * The CVS server has had the protocol check for unused data from the client
466 * A fix has been included that should avoid a very rare race condition that
467 could cause a CVS server to exit with a "broken pipe" message.
469 * Infinite alias loops in the modules file are now checked for and avoided.
471 * Clients on case insensitive systems now preserve the case of directories in
472 CVS/Entries, in addition to files, for use in communications with the CVS
475 * Misc status message fixes for consistency.
477 * Some previously untested behavior is now being tested.
479 * Server no longer claims to support the "Case" request.
481 * Case insensitive clients once again preserve the case of filenames in
482 CVS/Entries for communication with the server, as specified in the CVS
483 client/server protocol spec. Note that all CVS _servers_ still lack support
484 for case insensitive clients - servers are relying on the client to preserve
485 the case of checked out files.
487 * Thanks to Ville Skyttä the man page has a few less spelling errors and is
488 slightly more accurate.
490 * Thanks to Ville Skyttä some unused variables were removed from the log_accum
491 Perl script in contrib.
493 * Thanks to Alexey Mahotkin, a bug that prevented CVS from being compiled with
494 Kerberos 4 authentication enabled has been fixed.
496 * A minor bug that caused CVS to fail to report an inifinte alias loop in the
497 modules file when portions of the alias definition contained trailing slashes
500 * A bug in the gzip code that could cause heap corruption and segfaults in CVS
501 servers talking to clients less than 1.8 and some modern third-party CVS
502 clients has been fixed.
504 * mktemp.sh is now included with the source distribution so that the rcs2log
505 and cvsbug executables may be run on systems which do not contain an
506 implementation of mktemp.
508 * Misc documentation fixes.
512 * xmalloc, xstrdup, & some other memory allocating functions are now available
513 vi GNULIB versions imported into lib.
515 * The asnprintf() & vasnprintf() functions are now available due to a GNULIB
518 * Misc cosmetic, readability, and commenting fixes.
520 Changes between 1.12.4 and 1.12.5:
521 **********************************
523 SERVER SECURITY ISSUES
525 * pserver can no longer be configured to run as root via the
526 $CVSROOT/CVSROOT/passwd file, so if your passwd file is compromised, it no
527 longer leads directly to a root hack. Attempts to root will also be logged
532 * The Windows build files were updated to allow building of the current version
535 Changes between 1.12.3 and 1.12.4:
536 **********************************
540 * The CVS server no longer locks more than a directory at a time for write, so
541 large commits & tags should now have a much harder time blocking other
544 * Add support for large files. Use --disable-largefile to omit support
547 Changes between 1.12.2 and 1.12.3:
548 **********************************
550 SERVER SECURITY ISSUES
552 * Malformed module requests could cause the CVS server to attempt to create
553 directories and possibly files at the root of the filesystem holding the CVS
554 repository. Filesystem permissions usually prevent the creation of these
555 misplaced directories, but nevertheless, the CVS server now rejects the
560 * Support for case insensitive clients has been removed. This is not as
561 drastic as it sounds, as all of the current tests still pass without
562 modification when run from a case insensitive client to a case sensitive
563 server. In the end this should provide a major stability improvement.
565 * A minor problem that prevented the correct version of a system ZLIB from
566 being detected on some platforms has been fixed.
568 * Attempts to use the global `-l' option, removed from both client and server
569 as of version 1.12.1, will now elicit a warning rather than a fatal error
572 * The configure script now tests whether it is building CVS on a case
573 insensitive file system. If it is, CVS assumes that all file systems on this
574 platform will be case insensitive. This is useful for getting the case
575 insensitivity flag set correctly when compiling on Mac OS X and under Cygwin
576 on Windows. Autodetection can be overridden using the
577 --disable-case-sensitivity and --enable-case-sensitivity arguments to
582 * A new set of tests to test issues specific to case insensitive clients and
583 servers has also been added.
585 * Support has been added to the test suite to support testing over a :ext: link
586 to another machine, subject to some stringent requirements. This support can
587 be used, for instance, to test the operation of a case insensitive client
588 against a case sensitive server. Please see the comments in TEST and the
589 src/sanity.sh test script itself for more.
591 * We've standardized on Automake 1.7.9 to get a bug fix. See the note below
592 on the Autoconf upgrade for more details.
594 * We've standardized on Autoconf version 2.58 to avoid a bug and get at a few
595 new macros. Again, this should only really affect developers, though it is
596 possible that CVS will now compile on a few new platforms. Please see the
597 section of the INSTALL file about using the autotools if you are compiling
600 Changes between 1.12.1 and 1.12.2:
602 * Misc cleanup, reorganization, and other minor fixes.
604 * A behavior change in `cvs up -jrev1 -jrev2' for modified files with a base
605 revision of rev2 (ie, checked-out version matches rev2 and file has been
606 modified). The operation is no longer ignored and instead is passed to
607 diff3. This will potentially re-apply the diffs between the two revisions to
608 a modified local file. Status messages like from a standard merge have also
609 been added when the file would not or does not change due to this merge
610 request ("[file] already contains the changes between [revisions]...").
612 * A build problem that caused warnings and slower builds on systems without a
613 working getline() function (e.g. Mac OS X 10.1) has been fixed.
615 * A build problem that prevented the CVS executable from being built on systems
616 with the gettext library installed has been fixed.
618 * A bug which could stop `cvs admin -mTAG:message' from recursing has been
621 * Misc documentation cleanup and fixes.
623 * Some of the contrib scripts, some of the documentation, and sanity.sh were
624 modified to use and recommend more portable commands rather than using and
625 recommending commands which were not compatible with the POSIX 1003.1-2001
628 * CVS now knows how to report, as well as record, `P' record types.
630 * When running the `cvs history' command, clients will now send the
631 long-accepted `-e' option, for all records, rather than explicitly requesting
632 `P' record types, a request which servers prior to 1.11.7 will reject with a
635 * A problem with locating files requested by case insensitive clients which was
636 accidentally introduced in 1.11.6 as part of a fix for a data loss problem
637 involving `cvs add's from case insensitive clients has been fixed. The
638 relevant error message was `cvs [<command> aborted]: filE,v is ambiguous;
639 could mean FILE,v or file,v'.
641 * A problem in the CVS getpass library that could cause passwords to echo on
642 some systems has been fixed.
644 * A segfault that could occur in very rare cases where the stat of a file
645 failed during a diff has been fixed.
647 * Any user with write privleges to the CVSROOT/checkoutlist file could pass
648 arbitrary format strings directly through to a printf function. This was
649 probably bad and has been fixed. White space at the beginning of error strings
650 in checkoutlist is now ignored properly.
652 * A chmod 0600 that CVS performed on temp files it created designed to work
653 around a bug in versions of GLIBC eariler than 2.0.7 has been removed since it
654 still left a race condition open to exploitation and provided a false sense of
655 security. If you are linking CVS against a version of GLIBC prior to 2.0.7,
656 you should consider upgrading GLIBC.
658 * The CVSROOT/editinfo file is no longer referenced by CVS. This funcitonality
659 has been deprecated for over six years and removing it will presumably not
660 cause anyone any problems.
662 * In client/server mode, most messages from CVS now contain the actual
663 command name rather than the generic "server".
665 * A long-standing bug that prevented most client/server updates from being
666 logged in the history file has been fixed.
668 * Updates done via a patch ("P" status) are now logged in the history file
669 by default and the corresponding "P" history record type is now documented.
670 If you're setting the LogHistory option in your CVSROOT/config file, you may
671 want to add "P" to the list of record types.
673 * CVS now will always compile its own getpass() function (originally from
674 GNULIB) in favor of any system one that may exist. This avoids some problems
675 with long passwords on some systems and updates us to POSIX.2 compliance, since
676 getpass() was removed from the POSIX.2 specification.
678 * Support for pre-ANSI compilers has been removed. Our minimum support level
679 now assumes at least a freestanding C89 compilers. See the HACKING file for
680 more information. If you *really* need K&R support, our Makefile.am files
681 should only need minor tweaking to get them to run the ansi2knr script from the
682 Automake project. If you get this working, please send a patch to
685 * Experimental support for Pluggable Authentication Modules (PAM) has been
686 added, though it is not compiled by default. If you like this feature (or
687 don't), please send us feedback. See the Cederqvist, `./configure --help',
688 and the INSTALL file for more.
690 * Command line keyword expansion modes no longer override binary keyword
693 * New LocalKeyword and KeywordExpand options to CVSROOT/config which
694 FreeBSD, OpenBSD, and NetBSD users may find familiar as the "tag" and
695 "tagexpand" options used for many years. The CVSHeader keyword has
696 also been added to the mixture.
698 * A bug that allowed a write lock to be created in a directory despite
699 there being existing read locks when using LockDir in CVSROOT/config has
702 * A bug with short patches (`rdiff -s') which caused rdiff to sometimes report
703 differences that did not exist has been fixed.
705 * Some minor corrections were made to the diff code to keep diff & rdiff from
706 printing diff headers with empty change texts when two files have different
707 revision numbers but the same content.
709 * The global '-l' option, which suppressed history logging, has been removed
710 from both client and server.
712 Changes from 1.11.5 to 1.12.1:
714 * The new --with-external-zlib option can be passed to configure to compile
715 CVS against an external installed zlib.
717 * A warning message is now issued if an administrative file contains
718 more than one DEFAULT entry.
720 * An error running a verifymsg script (such as referencing an unset user
721 variable or the script not existing) now causes the verification to
724 * Errors in administrative files commands (like unset user variables)
725 are no longer reported unless the command is actually executed.
727 * When a file is initially checked out, its last access time is now set
728 to the current time rather than being set to the time the file was last
729 checked in like the modification time is.
731 * The Checkin.prog and Update.prog functionality has been removed. This
732 fuctionality previously allowed executables to be specified in the modules file
733 to be run at update and checkin time, but users could edit these files on a per
734 workspace basis, creating a security hole.
736 * CVSROOTs which contain a symlink to a real repository should work.
738 * contrib/rcs2log and src/cvsbug now use the BSD mktemp program to create
739 their temp files and directories on systems which provide it.
741 * Added a UserAdminOptions configuration option to CVSROOT/config to
742 control which `cvs admin' commands are not restricted to the `cvsadmin'
745 * If the rcsinfo specified template changes after a user has checked
746 out a tree, the template in the users' tree will be updated rather
747 than remaining static from the time of the original checkout.
749 * Added a CVSREADONLYFS environment variable and `-R' cvs global
750 option to turn on read-only repository mode for local repositories.
751 This allows users to checkout from a CDROM repository or other
752 read-only filesystem.
754 * There is a new CVS_LOCAL_BRANCH_NUM environment variable, which
755 may be used to give control over the branch number to be used next.
756 Useful for having local changes in a CVSup mirrored repository.
758 * Miscellaneous documentation corrections.
760 * Corrected the path in a failed write error message.
762 * Autoconf and Automake are no longer run automatically unless you run
763 configure with --enable-maintainer-mode. Accordingly, noautomake.sh is
764 no longer needed and has been removed.
766 * We've standardized on Automake version 1.7.5 and Autoconf version 2.57 to get
767 at a few new macros. Again, this should only really affect developers. See
768 the section of the INSTALL file about using the autotools if you are compiling
771 Changes from 1.11.4 to 1.11.5:
773 * Fixed a security hole in the CVS server by which users with read only access
774 could gain write access. This issue does not affect client builds. The
775 Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the
776 name CAN-2003-0015 to this issue. See
777 <http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0015> for more
780 * Fixed some bugs where revision numbers starting with 0 (like 0.3)
781 weren't correctly handled. (CVS doesn't normally use such revision
782 numbers, but users may be able to force it to do so and old RCS files
785 Changes from 1.11.3 to 1.11.4:
787 * Some minor changes to allow the code to compile on Windows platforms.
789 Changes from 1.11.2 to 1.11.3:
791 * The tag/rtag code has been fixed to once again lock just a single
794 * There was a bug where certain error conditions could cause the server
795 to go into an infinite loop. There was also a bug that caused a
796 compressed connection from an older client to hang on shutdown. These
797 bugs have been fixed.
799 * Fixed a bug that caused the server to reject most watch commands.
801 * When waiting for another user's lock, the message timestamps are now
802 in UTC rather than the server's local time.
804 * The options.h file is no longer used. This fixes a bug that occurred when
805 1.11.2 was compiled on Windows platforms.
807 * We've standardized on Automake version 1.6.3 and Autoconf version 2.53.
808 They are cleaner, less bug prone, and will hopfully allow me to start updating
809 sanity.sh to use Autotest and Autoshell. Again, this should only really affect
810 developers. See the section of the INSTALL file about using the autotools if
811 you are compiling CVS yourself.
813 * Fixed a bug in the log/rlog code when a revision range crosses a
816 * Fixed a bug where filenames starting with - would be misinterpreted as
817 options when using client/server mode.
819 Changes from 1.11.1p1 to 1.11.2:
821 * There is a new feature, enabled by RereadLogAfterVerify in CVSROOT/config,
822 which tells CVS to reread the log message after running the verifymsg
823 script. This allows the verifymsg script to reformat or otherwise
824 modify the log message.
826 * The interpretation of revision ranges using :: in "log" and "rlog"
827 has changed: a::b now excludes the log message from revision a but
828 includes the log message from revision b. Also, revision ranges that
829 cross branch points should now work.
831 * zlib has been updated to version 1.4. There is a security advisory
832 out in regards to 1.3. This should fix that problem.
834 * The "log" and "rlog" commands now have a -S option to suppress the
835 header information when no revisions are selected.
837 * A serious error that allowed read-only users to tag files has been
840 * The "annotate" command will no longer annotate binary files unless
841 you specify the new -F option.
843 * The "tag" and "rtag" commands will no longer move or delete branch
844 tags unless you use the new -B option. (This prevents accidental
845 changes to branch tags that are hard to undo.)
847 * We've standardized on the 1.5 Automake release for the moment. Again, this
848 should only really affect developers. See the section of the INSTALL file
849 about using the autotools if you are compiling CVS yourself.
851 Changes from 1.11.1 to 1.11.1p1:
853 * Read only access was broken - now fixed.
855 Changes from 1.11 to 1.11.1:
857 * There was a locking bug in the tag/rtag code that could lose changes
858 made to a file while the tag operation was in progress. This has been
859 fixed, but all of the directories being tagged are now locked for the
860 entire duration of the tag operation rather than only one directory at a
863 * The "cvs diff" command now accepts the -y/--side=by-side and -T/
864 --initial-tab options. (To use these options with a remote repository,
865 both the client and the server must support them.)
867 * The expansion of the loginfo format string has changed slightly.
868 Previously, the expansion was surrounded by single quotes ('); if a file
869 name contained a single quote character, the string would not be parsed
870 as a single entity by the Unix shell (and it would not be possible to
871 parse it unambiguously). Now the expansion is surrounded by double
872 quotes (") and any embedded dollar signs ($), backticks (`), backslashes
873 (\), and double quotes are preceded by a backslash. This is parsed as a
874 single entity by the shell reguardless of content. This change should
875 not be noticable unless you're not using a Unix shell or you have
876 embedded the format string inside a double quoted string.
878 * There was a bug in the diff code which sometimes caused conflicts to
879 be flagged which shouldn't have been. This has been fixed.
881 * New "cvs rlog" and "cvs rannotate" commands have been added to get log
882 messages and annotations without having to have a checked-out copy.
884 * Exclusive revision ranges have been added to "cvs log" using ::
885 (similar to "cvs admin -o").
887 * The VMS client now accepts wildcards if you're running VMS 7.x.
889 * ZLIB has been updated to version 1.1.3, the most current version. This
890 includes mostly some optimizations and minor bug fixes.
892 * The ~/.cvspass file has a slightly modified format. CVSROOTs are now
893 stored in a new canonical form - hostnames are now case insensitive and
894 port numbers are always stored in the new format. Until a new login for
895 a particular CVSROOT is performed with the new version of CVS, new and
896 old versions of CVS should interoperate invisibly. After that point, an
897 extra login using the old version of CVS may be necessary to continue to
898 allow the new and old versions of CVS to interoperate using the same
899 ~/.cvspass file and CVSROOT. The exception to this rule occurs when the
900 CVSROOTs used with the different versions use case insensitively
901 different hostnames, for example, "empress", and "empress.2-wit.com".
903 * A password and a port number may now be specified in CVSROOT for
904 pserver connections. The new format is:
906 :pserver:[[user][:password]@]host[:[port]]/path
908 Note that passwords specified in a checkout command will be saved in the
909 clear in the CVS/Root file in each created directory, so this is not
910 recommended, except perhaps when accessing anonymous repositories or the
913 * The distribution has been converted to use Automake. This shouldn't
914 affect most users except to ease some portability concerns, but if you
915 are building from the repository and encounter problems with the
916 makefiles, you might try running ./noautomake.sh after a fresh update
919 Changes from 1.10 to 1.11:
921 * The "cvs update" command has a new -C option to get clean copies from
922 the repository, abandoning any local changes.
924 * The new "cvs version" command gives a short version message. If
925 the repository is remote, both the client and server versions are
928 * "cvs admin -t" now works correctly in client/server mode.
930 * The "cvs history" command output format has changed -- the date
931 now includes the year and is given is ISO 8601 format (yyyy-mm-dd).
932 Also, the new LogHistory option in CVSROOT/config can be used to
933 control what information gets recorded in the log file and code has
934 been added to record file removals.
936 * The buggy PreservePermissions code has been disabled.
938 * Anonymous read-only access can now be done without requiring a
939 password. On the server side, simply give that user (presumably
940 `anonymous') an empty password in the CVSROOT/passwd file, and then
941 any received password will authenticate successfully.
943 * There is a new access method :fork: which is similar to :local:
944 except that it is implemented via the CVS remote protocol, and thus
945 has a somewhat different set of quirks and bugs.
947 * The -d command line option no longer updates the CVS/Root file. For
948 one thing, the CVS 1.9/1.10 behavior never had updated CVS/Root in
949 subdirectories, and for another, it didn't seem that popular in
950 general. So this change restores the CVS 1.8 behavior (which is also
951 the CVS 1.9/1.10 behavior if the environment variable
952 CVS_IGNORE_REMOTE_ROOT is set; with this change,
953 CVS_IGNORE_REMOTE_ROOT no longer has any effect).
955 * It is now possible for a single CVS command to recurse into several
956 CVS roots. This includes roots which are located on several servers,
957 or which are both remote and local. CVS will make connections to as
958 many servers as necessary.
960 * It is now possible to put the CVS lock files in a directory
961 set by the new LockDir option in CVSROOT/config. The default
962 continues to be to put the lock files in the repository itself.
964 Changes from 1.9 to 1.10:
966 * A bug was discovered in the -t/-f wrapper support that can cause
967 serious data loss. Because of this (and also the fact that it doesn't
968 work at all in client/server mode), the -t/-f wrapper code has been
969 disabled until it can be fixed.
971 * There is a new feature, enabled by TopLevelAdmin in CVSROOT/config,
972 which tells CVS to modify the behavior of the "checkout" command. The
973 command now creates a CVS directory at the top level of the new
974 working directory, in addition to CVS directories created within
975 checked-out directories. See the Cederqvist for details.
977 * There is an optional set of features, enabled by PreservePermissions
978 in CVSROOT/config, which allow CVS to store unix-specific file
979 information such as permissions, file ownership, and links. See the
980 Cederqvist for details.
982 * One can now authenticate and encrypt using the GSSAPI network
983 security interface. For details see the Cederqvist's description of
984 specifying :gserver: in CVSROOT, and the -a global option.
986 * All access to RCS files is now implemented internally rather than by
987 calling RCS programs. The main user-visible consequence of this is
988 that there is no need to worry about making sure that CVS finds the
989 correct version of RCS. The -b global option and the RCSBIN setting
990 in CVSROOT/config are still accepted but don't do anything. The
991 $RCSBIN internal variable in administrative files is no longer
994 * There is a new syntax, "cvs admin -orev1::rev2", which collapses the
995 revisions between rev1 and rev2 without deleting rev1 or rev2
998 * There is a new administrative file CVSROOT/config which allows one
999 to specify miscellaneous aspects of CVS configuration. Currently
1002 - SystemAuth, allows you to prevent pserver from checking for system
1003 usernames/passwords.
1005 For more information see the "config" section of cvs.texinfo.
1007 * When setting up the pserver server, one now must specify the
1008 allowable CVSROOT directories in inetd.conf. See the Password
1009 authentication server section of cvs.texinfo for details. Note that
1010 this implies that everyone who is running a pserver server must edit
1011 inetd.conf when upgrading their CVS.
1013 * The client no longer needs an external patch program (assuming both
1014 the client and the server have been updated to the new version).
1016 * "cvs admin [options]" will now recurse. In previous versions of
1017 CVS, it was an error and one needed to specify "cvs admin [options] ."
1018 to recurse. This change brings admin in line with the other CVS
1021 * New "logout" command to remove the password for a remote cvs
1022 repository from the cvspass file.
1024 * Read-only repository access is implemented for the
1025 password-authenticated server (other access methods are just governed
1026 by Unix file permissions, since they require login access to the
1027 repository machine anyway). See the "Repository" section of
1028 cvs.texinfo for details, including a discussion of security issues.
1029 Note that the requirement that read-only users be able to create locks
1030 and write the history file still applies.
1032 * There is a new administrative file verifymsg which is like editinfo
1033 but merely validates the message, rather than also getting it from the
1034 user. It therefore works with client/server CVS or if one uses the -m
1035 or -F options to commit. See the verifymsg section of cvs.texinfo for
1038 * The %s format formerly accepted in loginfo has been extended to
1039 formats such as %{sVv}, so that loginfo scripts have access to the
1040 version numbers being changed. See the Loginfo section of cvs.texinfo
1043 * The postscript documentation (doc/cvs.ps) shipped with CVS is now
1044 formatted for US letter size instead of A4. This is not because we
1045 consider this size "better" than A4, but because we believe that the
1046 US letter version will print better on A4 paper than the other way
1049 * The "cvs export" command is now logged in the history file and there
1050 is a "cvs history -x E" command to select history file entries
1053 * CVS no longer uses the CVS_PASSWORD environment variable. Storing
1054 passwords in cleartext in an environment variable is a security risk,
1055 especially since (on BSD variants) any user on the system can display
1056 any process's environment using 'ps'. Users should use the 'cvs
1057 login' command instead.
1060 Changes from 1.8 to 1.9:
1062 * Windows NT client should now work on Windows 95 as well.
1064 * New option "--help-synonyms" prints a list of all recognized command
1067 * The "log" command is now implemented internally rather than via the
1068 RCS "rlog" program. The main user-visible consequence is that
1069 symbolic branch names now work (for example "cvs log -rbranch1").
1070 Also, the date formats accepted by -d have changed. They previously
1071 had been a bewildering variety of poorly-documented date formats. Now
1072 they are the same as the date formats accepted by the -D options to
1073 the other CVS commands, which is also a (different) bewildering
1074 variety of poorly-documented date formats, but at least we are
1075 consistently bewildering :-).
1077 * Encryption is now supported over a Kerberos client/server
1078 connection. The new "-x" global option requests it. You must
1079 configure with the --enable-encryption option in order to enable
1082 * The format of the CVS commit message has changed slightly when
1083 committing changes on a branch. The tag on which the commit is
1084 ocurring is now reported correctly in all cases.
1086 * New flag -k in wrappers allows you to specify the keyword expansion
1087 mode for added files based on their name. For example, you can
1088 specify that files whose name matches *.exe are binary by default.
1089 See the Wrappers section of cvs.texinfo for more details.
1091 * Remote CVS with the "-z" option now uses the zlib library (included
1092 with CVS) to compress all communication between the client and the
1093 server, rather than invoking gzip on each file separately. This means
1094 that compression is better and there is no need for an external gzip
1095 program (except to interoperate with older version of CVS).
1097 * The "cvs rlog" command is deprecated and running it will print a
1098 warning; use the synonymous "cvs log" command instead. It is
1099 confusing for rlog to mean the same as log because some other CVS
1100 commands are in pairs consisting of a plain command which operates on
1101 a working directory and an "r" command which does not (diff/rdiff;
1104 * "cvs diff" has a bunch of new options, mostly long options. Most of
1105 these work only if rcsdiff and diff support them, and are named the
1106 same as the corresponding options to diff.
1108 * The -q and -Q command options to "cvs diff" were removed (use the
1109 global options instead). This brings "cvs diff" into line with the
1110 rest of the CVS commands.
1112 * The "annotate" command can now be used to annotate a revision other
1113 than the head revision on the trunk (see the -r, -D, and -f options in
1114 the annotate node of cvs.texinfo for details).
1116 * The "tag" command has a new option "-c" which checks that all files
1117 are not locally modified before tagging.
1119 * The -d command line option now overrides the cvsroot setting stored
1120 in the CVS/Root file in each working directory, and specifying -d will
1121 cause CVS/Root to be updated.
1123 * Local (non-client/server) CVS now runs on Windows NT. See
1124 windows-NT/README for details.
1126 * The CVSROOT variable specification has changed to support more
1127 access methods. In addition to "pserver," "server" (internal rsh
1128 client), "ext" (external rsh client), "kserver" (kerberos), and
1129 "local" (local filesystem access) can now be specified. For more
1130 details on each method, see cvs.texinfo (there is an index entry for
1131 :local: and each of the other access methods).
1133 * The "login" command no longer prompts the user for username and
1134 hostname, since one will have to provide that information via the `-d'
1135 flag or by setting CVSROOT.
1137 Changes from 1.7 to 1.8:
1139 * New "cvs annotate" command to display the last modification for each
1140 line of a file, with the revision number, user checking in the
1141 modification, and date of the modification. For more information see
1142 the `annotate' node in cvs.texinfo.
1144 * The cvsinit shell script has been replaced by a cvs init command.
1145 The cvs init command creates some example administrative files which
1146 are similar to the files found in the examples directory (and copied
1147 by cvsinit) in previous releases.
1149 * Added the patterns *.olb *.exe _$* *$ to default ignore list.
1151 * There is now a $USER internal variable for *info files.
1153 * There is no longer a separate `mkmodules' program; the functionality
1154 is now built into `cvs'. If upgrading an old repository, it is OK to
1155 leave in the lines in the modules file which run mkmodules (the
1156 mkmodules actions will get done twice, but that is harmless); you will
1157 probably want to remove them once you are no longer using the old CVS.
1159 * One can now specify user variables in *info files via the
1160 ${=varname} syntax; there is a -s global option to set them. See the
1161 Variables node in cvs.texinfo for details.
1163 Changes from 1.6 to 1.7:
1165 * The default ignore list has changed slightly: *.obj has been added
1166 and CVS* has been changed to CVS CVS.adm.
1168 * CVS now supports password authentication when accessing remote
1169 repositories; this is useful for sites that can't use rsh (because of
1170 a firewall, for example), and also don't have kerberos. See node
1171 "Password authenticated" (in "Remote repositories", in
1172 doc/cvs.texinfo) for more details. Note: This feature requires both
1173 the client and server to be upgraded.
1175 * Using the -kb option to specify binary files now works--most cases
1176 did not work before. See the "Binary files" section of
1177 doc/cvs.texinfo for details.
1179 * New developer communication features. See the "Watches" section of
1180 doc/cvs.texinfo for details.
1182 * RCS keyword "Name" supported for "cvs update -r <tag>" and "cvs
1185 * If there is a group whose name matches a compiled in value which
1186 defaults to "cvsadmin", only members of that group can use "cvs
1187 admin". This replaces the CVS_NOADMIN option.
1189 * CVS now sets the modes of files in the repository based on the
1190 CVSUMASK environment variable or a compiled in value defaulting to
1191 002. This way other developers will be able to access the files in
1192 the repository regardless of the umask of the developer creating them.
1194 * The command names in .cvsrc now match the official name of the
1195 command, not the one (possibly an alias) by which it was invoked. If
1196 you had previously relied on "cvs di" and "cvs diff" using different
1197 options, instead use a shell function or alias (for example "alias
1198 cvsdi='cvs diff -u'"). You also can specify global CVS options (like
1199 "-z") using the command name "cvs".
1201 Changes from 1.5 to 1.6:
1203 * Del updated the man page to include all of the new features
1206 * "cvs tag" now supports a "-r | -D" option for tagging an already
1207 tagged revision / specific revision of a file.
1209 * There is a "taginfo" file in CVSROOT that supports filtering and
1210 recording of tag operations.
1212 * Long options support added, including --help and --version options.
1214 * "cvs release" no longer cares whether or not the directory being
1215 released has an entry in the `modules' file.
1217 * The modules file now takes a -e option which is used instead of -o
1218 for "cvs export". If your modules file has a -o option which you want
1219 to be used for "cvs export", change it to specify -e as well as -o.
1221 * "cvs export" now takes a -k option to set RCS keyword expansion.
1222 This way you can export binary files. If you want the old behavior,
1223 you need to specify -kv.
1225 * "cvs update", "cvs rdiff", "cvs checkout", "cvs import", "cvs
1226 release", "cvs rtag", and "cvs tag" used to take -q and -Q options
1227 after the command name (e.g. "cvs update -q"). This was confusing
1228 because other commands, such as "cvs ci", did not. So the options
1229 after the command name have been removed and you must now specify, for
1230 example, "cvs -q update", which has been supported since CVS 1.3.
1232 * New "wrappers" feature. This allows you to set a hook which
1233 transforms files on their way in and out of cvs (apparently on the
1234 NeXT there is some particular usefulness in tarring things up in the
1235 repository). It also allows you to declare files as merge-by-copy
1236 which means that instead of trying to merge the file, CVS will merely
1237 copy the new version. There is a CVSROOT/cvswrappers file and an
1238 optionsl ~/.cvswrappers file to support this feature.
1240 * You can set CVSROOT to user@host:dir, not just host:dir, if your
1241 username on the server host is different than on the client host.
1243 * VISUAL is accepted as well as EDITOR.
1245 * $CVSROOT is expanded in *info files.
1247 Changes from 1.4A2 to 1.5:
1249 * Remote implementation. This is very helpful when collaborating on a
1250 project with someone across a wide-area network. This release can
1251 also be used locally, like other CVS versions, if you have no need for
1254 Here are some of the features of the remote implementation:
1255 - It uses reliable transport protocols (TCP/IP) for remote repository
1256 access, not NFS. NFS is unusable over long distances (and sometimes
1257 over short distances)
1258 - It transfers only those files that have changed in the repository or
1259 the working directory. To save transmission time, it will transfer
1260 patches when appropriate, and can compress data for transmission.
1261 - The server never holds CVS locks while waiting for a reply from the client;
1262 this makes the system robust when used over flaky networks.
1264 The remote features are documented in doc/cvsclient.texi in the CVS
1265 distribution, but the main doc file, cvs.texinfo, has not yet been
1266 updated to include the remote features.
1268 * Death support. See src/README-rm-add for more information on this.
1270 * Many speedups, especially from jtc@cygnus.com.
1272 * CVS 1.2 compatibility code has been removed as a speedup. If you
1273 have working directories checked out by CVS 1.2, CVS 1.3 or 1.4A2 will
1274 try to convert them, but CVS 1.5 and later will not (if the working
1275 directory is up to date and contains no extraneous files, you can just
1276 remove it, and then check out a new working directory). Likewise if
1277 your repository contains a CVSROOT.adm directory instead of a CVSROOT
1278 directory, you need to rename it.
1280 Fri Oct 21 20:58:54 1994 Brian Berliner <berliner@sun.com>
1282 * Changes between CVS 1.3 and CVS 1.4 Alpha-2
1284 * A new program, "cvsbug", is provided to let you send bug reports
1285 directly to the CVS maintainers. Please use it instead of sending
1286 mail to the info-cvs mailing list. If your build fails, you may
1287 have to invoke "cvsbug" directly from the "src" directory as
1290 * A new User's Guide and Tutorial, written by Per Cederqvist
1291 <ceder@signum.se> of Signum Support. See the "doc" directory. A
1292 PostScript version is included as "doc/cvs.ps".
1294 * The Frequesntly Asked Questions file, FAQ, has been added to the
1295 release. Unfortunately, its contents are likely out-of-date.
1297 * The "cvsinit" shell script is now installed in the $prefix/bin
1298 directory like the other programs. You can now create new
1299 CVS repositories with great ease.
1301 * Index: lines are now printed on output from 'diff' and 'rdiff',
1302 in order to facilitate application of patches to multiple subdirs.
1304 * Support for a ~/.cvsrc file, which allows you to specify options
1305 that are always supposed to be given to a specific command. This
1306 feature shows the non-orthogonality of the option set, since while
1307 there may be an option to turn something on, the option to turn
1308 that same thing off may not exist.
1310 * You can now list subdirectories that you wish to ignore in a
1311 modules listing, such as:
1313 gcc -a gnu/gcc, !gnu/gcc/testsuites
1315 which will check out everything underneath gnu/gcc, except
1316 everything underneath gnu/gcc/testsuites.
1318 * It is now much harder to accidentally overwrite an existing tag
1319 name, since attempting to move a tag name will result in a error,
1320 unless the -F (force) flag is given to the tag subcommands.
1322 * Better error checking on matching of the repository used to
1323 check code out from against the repository the current cvs
1324 commnands would use. (Thanks to Mark Baushke <mdb@cisco.com>)
1326 * Better support for sites with multiple CVSROOT repositories has
1327 been contributed. The file "CVS/Root" in your working directory
1328 is created to hold the full path to the CVS repository and a
1329 simple check is made against your current CVSROOT setting.
1331 * You can now specify an RCS keyword substitution value when you
1332 import files into the repository.
1334 * Uses a much newer version of Autoconf, and conforms to the GNU
1335 coding standards much more closely. No, it still doesn't have
1338 * Code cleanup. Many passes through gcc -Wall helped to identify
1339 a number of questionable constructs. Most arbitrary length limits
1342 * Profiling to determine bottlenecks helped to identify the best
1343 places to spend time speeding up the code, which was then done. A
1344 number of performance enhancements in filename matching have sped
1347 * Many more contributions have been added to the "contrib"
1348 directory. See the README file in that directory for more
1351 * "cvs commit" will try harder to not change the file's
1352 modification time after the commit. If the file does not change
1353 as a result of the commit operation, CVS will preserve the
1354 original modification time, thus speeding up future make-type
1357 * "cvs commit" now includes any removed files in the (optional)
1358 pre-commit checking program that may be invoked. Previously, only
1359 added and modified files were included.
1361 * It is now possible to commit a file directly onto the trunk at a
1362 specific revision level by doing "cvs commit -r3.0 file.c", where
1363 "3.0" specifies the revision you wish to create. The file must be
1364 up-to-date with the current head of the trunk for this to succeed.
1366 * "cvs commit" will now function with a pre-commit program that
1367 has arguments specified in the "commitinfo" file.
1369 * The "mkmodules" program will now look within the
1370 $CVSROOT/CVSROOT/checkoutlist" file for any additional files that
1371 should be automatically checked out within CVSROOT; mkmodules also
1372 tries harder to preserve any execute bits the files may have
1375 * "cvs diff" is much more accurate about its exit status now. It
1376 now returns the maximum exit status of any invoked diff.
1378 * The "-I !" option is now supported for the import and update
1379 commands correctly. It will properly clear the ignore list now.
1381 * Some problems with "cvs import" handling of .cvsignore have been
1382 fixed; as well, some rampant recursion problems with import have
1385 * "cvs rdiff" (aka "cvs patch") now tries to set the modify time
1386 of any temporary files it uses to match those specified for the
1387 particular revision. This allows a more accurate patch image to
1390 * "cvs status" has improved revision descriptions. "Working
1391 revision" is used for the revision of the working file that you
1392 edit directly; "Repository revision" is the revision of the file
1393 with the $CVSROOT source repository. Also, the output is clearer
1394 with regard to sticky and branch revisions.
1396 * CVS no longer dumps core when given a mixture of directories and
1397 files in sub-directories (as in "cvs ci file1 dir1/file2").
1398 Instead, arguments are now clumped into their respective directory
1399 and operated on in chunks, together.
1401 * If the CVSEDITOR environment variable is set, that editor is
1402 used for log messages instead of the EDITOR environment variable.
1403 This makes it easy to substitute intelligent programs to make more
1404 elaborate log messages. Contributed by Mark D Baushke
1407 * Command argument changes:
1408 cvs: The "-f" option has been added to ignore
1410 commit: Renamed the "-f logfile" option to the
1411 "-F logfile" option. Added the "-f"
1412 option to force a commit of the specified
1413 files (this disables recursion).
1414 history: Added "-t timezone" option to force any
1415 date-specific output into the specified
1417 import: Added "-d" option to use the file's
1418 modification time as the time of the
1419 import. Added "-k sub" option to set the
1420 default RCS keyword substitution mode for
1421 newly-created files.
1422 remove: Added "-f" option to force the file's
1423 automatic removal if it still exists in
1424 the working directory (use with caution).
1425 rtag: Added "-F" option to move the tag if it
1426 already exists -- new default is to NOT
1427 move tags automatically.
1428 tag: Added "-F" option to move the tag if it
1429 already exists -- new default is to NOT
1430 move tags automatically.
1432 Tue Apr 7 15:55:25 1992 Brian Berliner (berliner at sun.com)
1434 * Changes between CVS 1.3 Beta-3 and official CVS 1.3!
1436 * A new shell script is provided, "./cvsinit", which can be run at
1437 install time to help setup your $CVSROOT area. This can greatly
1438 ease your entry into CVS usage.
1440 * The INSTALL file has been updated to include the machines on
1441 which CVS has compiled successfully. I think CVS 1.3 is finally
1442 portable. Thanks to all the Beta testers!
1444 * Support for the "editinfo" file was contributed. This file
1445 (located in $CVSROOT/CVSROOT) can be used to specify a special
1446 "editor" to run on a per-directory basis within the repository,
1447 instead of the usual user's editor. As such, it can verify that
1448 the log message entered by the user is of the appropriate form
1449 (contains a bugid and test validation, for example).
1451 * The manual pages cvs(1) and cvs(5) have been updated.
1453 * The "mkmodules" command now informs you when your modules file
1454 has duplicate entries.
1456 * The "add" command now preserves any per-directory sticky tag when
1457 you add a new directory to your checked-out sources.
1459 * The "admin" command is now a fully recursive interface to the
1460 "rcs" program which operates on your checked-out sources. It no
1461 longer requires you to specify the full path to the RCS file.
1463 * The per-file sticky tags can now be effectively removed with
1464 "cvs update -A file", even if you had checked out the whole
1465 directory with a per-directory sticky tag. This allows a great
1466 deal of flexibility in managing the revisions that your checked-out
1467 sources are based upon (both per-directory and per-file sticky
1470 * The "cvs -n commit" command now works, to show which files are
1471 out-of-date and will cause the real commit to fail, or which files
1472 will fail any pre-commit checks. Also, the "cvs -n import ..."
1473 command will now show you what it would've done without actually
1476 * Doing "cvs commit modules" to checkin the modules file will no
1477 properly run the "mkmodules" program (assuming you have setup your
1478 $CVSROOT/CVSROOT/modules file to do so).
1480 * The -t option in the modules file (which specifies a program to
1481 run when you do a "cvs rtag" operation on a module) now gets the
1482 symbolic tag as the second argument when invoked.
1484 * When the source repository is locked by another user, that user's
1485 login name will be displayed as the holder of the lock.
1487 * Doing "cvs checkout module/file.c" now works even if
1488 module/file.c is in the Attic (has been removed from main-line
1491 * Doing "cvs commit */Makefile" now works as one would expect.
1492 Rather than trying to commit everything recursively, it will now
1493 commit just the files specified.
1495 * The "cvs remove" command is now fully recursive. To schedule a
1496 file for removal, all you have to do is "rm file" and "cvs rm".
1497 With no arguments, "cvs rm" will schedule all files that have been
1498 physically removed for removal from the source repository at the
1501 * The "cvs tag" command now prints "T file" for each file that was
1502 tagged by this invocation and "D file" for each file that had the
1503 tag removed (as with "cvs tag -d").
1505 * The -a option has been added to "cvs rtag" to force it to clean
1506 up any old, matching tags for files that have been removed (in the
1507 Attic) that may not have been touched by this tag operation. This
1508 can help keep a consistent view with your tag, even if you re-use
1511 Sat Feb 29 16:02:05 1992 Brian Berliner (berliner at sun.com)
1513 * Changes between CVS 1.3 Beta-2 and CVS 1.3 Beta-3
1515 * Many portability fixes, thanks to all the Beta testers! With any
1516 luck, this Beta release will compile correctly on most anything.
1517 Hey, what are we without our dreams.
1519 * CVS finally has support for doing isolated development on a
1520 branch off the current (or previous!) revisions. This is also
1521 extremely nice for generating patches for previously released
1522 software while development is progressing on the next release.
1523 Here's an example of creating a branch to fix a patch with the 2.0
1524 version of the "foo" module, even though we are already well into
1525 the 3.0 release. Do:
1527 % cvs rtag -b -rFOO_2_0 FOO_2_0_Patch foo
1528 % cvs checkout -rFOO_2_0_Patch foo
1533 A physical branch will be created in the RCS file only when you
1534 actually commit the change. As such, forking development at some
1535 random point in time is extremely light-weight -- requiring just a
1536 symbolic tag in each file until a commit is done. To fork
1537 development at the currently checked out sources, do:
1539 % cvs tag -b Personal_Hack
1540 % cvs update -rPersonal_Hack
1544 Now, if you decide you want the changes made in the Personal_Hack
1545 branch to be merged in with other changes made in the main-line
1546 development, you could do:
1548 % cvs commit # to make Personal_Hack complete
1549 % cvs update -A # to update sources to main-line
1550 % cvs update -jPersonal_Hack # to merge Personal_Hack
1552 to update your checked-out sources, or:
1554 % cvs checkout -jPersonal_Hack module
1556 to checkout a fresh copy.
1558 To support this notion of forked development, CVS reserves
1559 all even-numbered branches for its own use. In addition, CVS
1560 reserves the ".0" and ".1" branches. So, if you intend to do your
1561 own branches by hand with RCS, you should use odd-numbered branches
1562 starting with ".3", as in "1.1.3", "1.1.5", 1.2.9", ....
1564 * The "cvs commit" command now supports a fully functional -r
1565 option, allowing you to commit your changes to a specific numeric
1566 revision or symbolic tag with full consistency checks. Numeric
1567 tags are useful for bringing your sources all up to some revision
1572 For symbolic tags, you can only commit to a tag that references a
1573 branch in the RCS file. One created by "cvs rtag -b" or from
1574 "cvs tag -b" is appropriate (see below).
1576 * Roland Pesch <pesch@cygnus.com> and K. Richard Pixley
1577 <rich@cygnus.com> were kind enough to contribute two new manual
1578 pages for CVS: cvs(1) and cvs(5). Most of the new CVS 1.3 features
1579 are now documented, with the exception of the new branch support
1580 added to commit/rtag/tag/checkout/update.
1582 * The -j options of checkout/update have been added. The "cvs join"
1583 command has been removed.
1585 With one -j option, CVS will merge the changes made between the
1586 resulting revision and the revision that it is based on (e.g., if
1587 the tag refers to a branch, CVS will merge all changes made in
1588 that branch into your working file).
1590 With two -j options, CVS will merge in the changes between the two
1591 respective revisions. This can be used to "remove" a certain delta
1592 from your working file. E.g., If the file foo.c is based on
1593 revision 1.6 and I want to remove the changes made between 1.3 and
1596 % cvs update -j1.5 -j1.3 foo.c # note the order...
1598 In addition, each -j option can contain on optional date
1599 specification which, when used with branches, can limit the chosen
1600 revision to one within a specific date. An optional date is
1601 specified by adding a colon (:) to the tag, as in:
1603 -jSymbolic_Tag:Date_Specifier
1605 An example might be what "cvs import" tells you to do when you have
1606 just imported sources that have conflicts with local changes:
1608 % cvs checkout -jTAG:yesterday -jTAG module
1610 which tells CVS to merge in the changes made to the branch
1611 specified by TAG in the last 24 hours. If this is not what is
1612 intended, substitute "yesterday" for whatever format of date that
1613 is appropriate, like:
1615 % cvs checkout -jTAG:'1 week ago' -jTAG module
1617 * "cvs diff" now supports the special tags "BASE" and "HEAD". So,
1620 % cvs diff -u -rBASE -rHEAD
1622 will effectively show the changes made by others (in unidiff
1623 format) that will be merged into your working sources with your
1624 next "cvs update" command. "-rBASE" resolves to the revision that
1625 your working file is based on. "-rHEAD" resolves to the current
1626 head of the branch or trunk that you are working on.
1628 * The -P option of "cvs checkout" now means to Prune empty
1629 directories, as with "update". The default is to not remove empty
1630 directories. However, if you do "checkout" with any -r options, -P
1631 will be implied. I.e., checking out with a tag will cause empty
1632 directories to be pruned automatically.
1634 * The new file INSTALL describes how to install CVS, including
1635 detailed descriptions of interfaces to "configure".
1637 * The example loginfo file in examples/loginfo has been updated to
1638 use the perl script included in contrib/log.pl. The nice thing
1639 about this log program is that it records the revision numbers of
1640 your change in the log message.
1642 Example files for commitinfo and rcsinfo are now included in the
1645 * All "#if defined(__STDC__) && __STDC__ == 1" lines have been
1646 changed to be "#if __STDC__" to fix some problems with the former.
1648 * The lib/regex.[ch] files have been updated to the 1.3 release of
1649 the GNU regex package.
1651 * The ndbm emulation routines included with CVS 1.3 Beta-2 in the
1652 src/ndbm.[ch] files has been moved into the src/myndbm.[ch] files
1653 to avoid any conflict with the system <ndbm.h> header file. If
1654 you had a previous CVS 1.3 Beta release, you will want to "cvs
1655 remove ndbm.[ch]" form your copy of CVS as well.
1657 * "cvs add" and "cvs remove" are a bit more verbose, telling you
1658 what to do to add/remove your file permanently.
1660 * We no longer mess with /dev/tty in "commit" and "add".
1662 * More things are quiet with the -Q option set.
1664 * New src/config.h option: If CVS_BADROOT is set, CVS will not
1665 allow people really logged in as "root" to commit changes.
1667 * "cvs diff" exits with a status of 0 if there were no diffs, 1 if
1668 there were diffs, and 2 if there were errors.
1670 * "cvs -n diff" is now supported so that you can still run diffs
1671 even while in the middle of committing files.
1673 * Handling of the CVS/Entries file is now much more robust.
1675 * The default file ignore list now includes "*.so".
1677 * "cvs import" did not expand '@' in the log message correctly. It
1678 does now. Also, import now uses the ignore file facility
1681 Import will now tell you whether there were conflicts that need to
1682 be resolved, and how to resolve them.
1684 * "cvs log" has been changed so that you can "log" things that are
1685 not a part of the current release (in the Attic).
1687 * If you don't change the editor message on commit, CVS now prompts
1688 you with the choice:
1690 !)reuse this message unchanged for remaining dirs
1692 which allows you to tell CVS that you have no intention of changing
1693 the log message for the remainder of the commit.
1695 * It is no longer necessary to have CVSROOT set if you are using
1696 the -H option to get Usage information on the commands.
1698 * Command argument changes:
1699 checkout: -P handling changed as described above.
1700 New -j option (up to 2 can be specified)
1701 for doing rcsmerge kind of things on
1703 commit: -r option now supports committing to a
1704 numeric or symbolic tags, with some
1705 restrictions. Full consistency checks will
1707 Added "-f logfile" option, which tells
1708 commit to glean the log message from the
1709 specified file, rather than invoking the
1711 rtag: Added -b option to create a branch tag,
1712 useful for creating a patch for a previous
1713 release, or for forking development.
1714 tag: Added -b option to create a branch tag,
1715 useful for creating a patch for a previous
1716 release, or for forking development.
1717 update: New -j option (up to 2 can be specified)
1718 for doing rcsmerge kind of things on
1721 Thu Jan 9 10:51:35 MST 1992 Jeff Polk (polk at BSDI.COM)
1723 * Changes between CVS 1.3 Beta-1 and CVS 1.3 Beta-2
1725 * Thanks to K. Richard Pixley at Cygnus we now have function
1726 prototypes in all the files
1728 * Some small changes to configure for portability. There have
1729 been other portability problems submitted that have not been fixed
1730 (Brian will be working on those). Additionally all __STDC__
1731 tests have been modified to check __STDC__ against the constant 1
1732 (this is what the Second edition of K&R says must be true).
1734 * Lots of additional error checking for forked processes (run_exec)
1735 (thanks again to K. Richard Pixley)
1737 * Lots of miscellaneous bug fixes - including but certainly not
1739 various commit core dumps
1740 various update core dumps
1741 bogus results from status with numeric sticky tags
1742 commitprog used freed memory
1743 Entries file corruption caused by No_Difference
1744 commit to revision broken (now works if branch exists)
1745 ignore file processing broken for * and !
1746 ignore processing didn't handle memory reasonably
1747 miscellaneous bugs in the recursion processor
1748 file descriptor leak in ParseInfo
1749 CVSROOT.adm->CVSROOT rename bug
1752 * Reformatted all the code in src (with GNU indent) and then
1753 went back and fixed prototypes, etc since indent gets confused. The
1754 rationale is that it is better to do it sooner than later and now
1755 everything is consistent and will hopefully stay that way.
1756 The basic options to indent were: "-bad -bbb -bap -cdb -d0 -bl -bli0
1757 -nce -pcs -cs -cli4 -di1 -nbc -psl -lp -i4 -ip4 -c41" and then
1758 miscellaneous formatting fixes were applied. Note also that the
1759 "-nfc1" or "-nfca" may be appropriate in files where comments have
1760 been carefully formatted (e.g, modules.c).
1762 Sat Dec 14 20:35:22 1991 Brian Berliner (berliner at sun.com)
1764 * Changes between CVS 1.2 and CVS 1.3 Beta are described here.
1766 * Lots of portability work. CVS now uses the GNU "configure"
1767 script to dynamically determine the features provided by your
1768 system. It probably is not foolproof, but it is better than
1769 nothing. Please let me know of any portability problems. Some
1770 file names were changed to fit within 14-characters.
1772 * CVS has a new RCS parser that is much more flexible and
1773 extensible. It should read all known RCS ",v" format files.
1775 * Most of the commands now are fully recursive, rather than just
1776 operating on the current directory alone. This includes "commit",
1777 which makes it real easy to do an "atomic" commit of all the
1778 changes made to a CVS hierarchy of sources. Most of the commands
1779 also correctly handle file names that are in directories other than
1780 ".", including absolute path names. Commands now accept the "-R"
1781 option to force recursion on (though it is always the default now)
1782 and the "-l" option to force recursion off, doing just "." and not
1783 any sub-directories.
1785 * CVS supports many of the features provided with the RCS 5.x
1786 distribution - including the new "-k" keyword expansion options. I
1787 recommend using RCS 5.x (5.6 is the current official RCS version)
1788 and GNU diff 1.15 (or later) distributions with CVS.
1790 * Checking out files with symbolic tags/dates is now "sticky", in
1791 that CVS remembers the tag/date used for each file (and directory)
1792 and will use that tag/date automatically on the next "update" call.
1793 This stickyness also holds for files checked out with the the new
1794 RCS 5.x "-k" options.
1796 * The "cvs diff" command now recognizes all of the rcsdiff 5.x
1797 options. Unidiff format is available by installing the GNU
1798 diff 1.15 distribution.
1800 * The old "CVS.adm" directories created on checkout are now called
1801 "CVS" directories, to look more like "RCS" and "SCCS". Old CVS.adm
1802 directories are automagically converted to CVS directories. The
1803 old "CVSROOT.adm" directory within the source repository is
1804 automagically changed into a "CVSROOT" directory as well.
1806 * Symbolic links in the source repository are fully supported ONLY
1807 if you use RCS 5.6 or later and (of course) your system supports
1810 * A history database has been contributed which maintains the
1811 history of certain CVS operations, as well as providing a wide array
1812 of querying options.
1814 * The "cvs" program has a "-n" option which can be used with the
1815 "update" command to show what would be updated without actually
1816 doing the update, like: "cvs -n update". All usage statements
1817 have been cleaned up and made more verbose.
1819 * The module database parsing has been rewritten. The new format
1820 is compatible with the old format, but with much more
1821 functionality. It allows modules to be created that grab pieces or
1822 whole directories from various different parts of your source
1823 repository. Module-relative specifications are also correctly
1824 recognized now, like "cvs checkout module/file.c".
1826 * A configurable template can be specified such that on a "commit",
1827 certain directories can supply a template that the user must fill
1828 before completing the commit operation.
1830 * A configurable pre-commit checking program can be specified which
1831 will run to verify that a "commit" can happen. This feature can be
1832 used to restrict certain users from changing certain pieces of the
1833 source repository, or denying commits to the entire source
1836 * The new "cvs export" command is much like "checkout", but
1837 establishes defaults suitable for exporting code to others (expands
1838 out keywords, forces the use of a symbolic tag, and does not create
1839 "CVS" directories within the checked out sources.
1841 * The new "cvs import" command replaces the deprecated "checkin"
1842 shell script and is used to import sources into CVS control. It is
1843 also much faster for the first-time import. Some algorithmic
1844 improvements have also been made to reduce the number of
1845 conflicting files on next-time imports.
1847 * The new "cvs admin" command is basically an interface to the
1848 "rcs" program. (Not yet implemented very well).
1850 * Signal handling (on systems with BSD or POSIX signals) is much
1851 improved. Interrupting CVS now works with a single interrupt!
1853 * CVS now invokes RCS commands by direct fork/exec rather than
1854 calling system(3). This improves performance by removing a call to
1855 the shell to parse the arguments.
1857 * Support for the .cvsignore file has been contributed. CVS will
1858 now show "unknown" files as "? filename" as the result of an "update"
1859 command. The .cvsignore file can be used to add files to the
1860 current list of ignored files so that they won't show up as unknown.
1862 * Command argument changes:
1863 cvs: Added -l to turn off history logging.
1864 Added -n to show what would be done without actually
1866 Added -q/-Q for quiet and really quiet settings.
1867 Added -t to show debugging trace.
1868 add: Added -k to allow RCS 5.x -k options to be specified.
1869 admin: New command; an interface to rcs(1).
1870 checkout: Added -A to reset sticky tags/date/options.
1871 Added -N to not shorten module paths.
1872 Added -R option to force recursion.
1873 Changed -p (prune empty directories) to -P option.
1874 Changed -f option; forcing tags match is now default.
1875 Added -p option to checkout module to standard output.
1876 Added -s option to cat the modules db with status.
1877 Added -d option to checkout in the specified directory.
1878 Added -k option to use RCS 5.x -k support.
1879 commit: Removed -a option; use -l instead.
1881 Added -l option to disable recursion.
1882 Added -R option to force recursion.
1883 If no files specified, commit is recursive.
1884 diff: Now recognizes all RCS 5.x rcsdiff options.
1885 Added -l option to disable recursion.
1886 Added -R option to force recursion.
1887 history: New command; displays info about CVS usage.
1888 import: Replaces "checkin" shell script; imports sources
1889 under CVS control. Ignores files on the ignore
1890 list (see -I option or .cvsignore description above).
1891 export: New command; like "checkout", but w/special options
1892 turned on by default to facilitate exporting sources.
1893 join: Added -B option to join from base of the branch;
1894 join now defaults to only joining with the top two
1895 revisions on the branch.
1896 Added -k option for RCS 5.x -k support.
1897 log: Supports all RCS 5.x options.
1898 Added -l option to disable recursion.
1899 Added -R option to force recursion.
1900 patch: Changed -f option; forcing tags match is now default.
1901 Added -c option to force context-style diffs.
1902 Added -u option to support unidiff-style diffs.
1903 Added -V option to support RCS specific-version
1904 keyword expansion formats.
1905 Added -R option to force recursion.
1906 remove: No option changes. It's a bit more verbose.
1907 rtag: Equivalent to the old "cvs tag" command.
1908 No option changes. It's a lot faster for re-tag.
1909 status: New output formats with more information.
1910 Added -l option to disable recursion.
1911 Added -R option to force recursion.
1912 Added -v option to show symbolic tags for files.
1913 tag: Functionality changed to tag checked out files
1914 rather than modules; use "rtag" command to get the
1915 old "cvs tag" behaviour.
1916 update: Added -A to reset sticky tags/date/options.
1917 Changed -p (prune empty directories) to -P option.
1918 Changed -f option; forcing tags match is now default.
1919 Added -p option to checkout module to standard output.
1920 Added -I option to add files to the ignore list.
1921 Added -R option to force recursion.
1925 * Jeff Polk <polk@bsdi.com> rewrote most of the grody code of CVS
1926 1.2. He made just about everything dynamic (by using malloc),
1927 added a generic hashed list manager, re-wrote the modules database
1928 parsing in a compatible - but extended way, generalized directory
1929 hierarchy recursion for virtually all the commands (including
1930 commit!), generalized the loginfo file to be used for pre-commit
1931 checks and commit templates, wrote a new and flexible RCS parser,
1932 fixed an uncountable number of bugs, and helped in the design of
1933 future CVS features. If there's anything gross left in CVS, it's
1936 * David G. Grubbs <dgg@odi.com> contributed the CVS "history" and
1937 "release" commands. As well as the ever-so-useful "-n" option of
1938 CVS which tells CVS to show what it would do, without actually
1939 doing it. He also contributed support for the .cvsignore file.
1941 * Paul Sander, HaL Computer Systems, Inc. <paul@hal.com> wrote and
1942 contributed the code in lib/sighandle.c. I added support for
1943 POSIX, BSD, and non-POSIX/non-BSD systems.
1945 * Free Software Foundation contributed the "configure" script and
1946 other compatibility support in the "lib" directory, which will help
1947 make CVS much more portable.
1949 * Many others have contributed bug reports and enhancement requests.
1950 Some have even submitted actual code which I have not had time yet
1951 to integrate into CVS. Maybe for the next release.
1953 * Thanks to you all!
1955 Wed Feb 6 10:10:58 1991 Brian Berliner (berliner at sun.com)
1957 * Changes from CVS 1.0 Patchlevel 1 to CVS 1.0 Patchlevel 2; also
1958 known as "Changes from CVS 1.1 to CVS 1.2".
1960 * Major new support with this release is the ability to use the
1961 recently-posted RCS 5.5 distribution with CVS 1.2. See below for
1962 other assorted bug-fixes that have been thrown in.
1964 * ChangeLog (new): Added Emacs-style change-log file to CVS 1.2
1965 release. Chronological description of changes between release.
1967 * README: Small fixes to installation instructions. My email
1968 address is now "berliner@sun.com".
1970 * src/Makefile: Removed "rcstime.h". Removed "depend" rule.
1972 * src/partime.c: Updated to RCS 5.5 version with hooks for CVS.
1973 * src/maketime.c: Updated to RCS 5.5 version with hooks for CVS.
1974 * src/rcstime.h: Removed from the CVS 1.2 distribution.
1975 Thanks to Paul Eggert <eggert@twinsun.com> for these changes.
1977 * src/checkin.csh: Support for RCS 5.5 parsing.
1978 Thanks to Paul Eggert <eggert@twinsun.com> for this change.
1980 * src/collect_sets.c (Collect_Sets): Be quieter if "-f" option is
1981 specified. When checking out files on-top-of other files that CVS
1982 doesn't know about, run a diff in the hopes that they are really
1983 the same file before aborting.
1985 * src/commit.c (branch_number): Fix for RCS 5.5 parsing.
1986 Thanks to Paul Eggert <eggert@twinsun.com> for this change.
1988 * src/commit.c (do_editor): Bug fix - fprintf missing argument
1989 which sometimes caused core dumps.
1991 * src/modules.c (process_module): Properly NULL-terminate
1992 update_dir[] in all cases.
1994 * src/no_difference.c (No_Difference): The wrong RCS revision was
1995 being registered in certain (strange) cases.
1997 * src/patch.c (get_rcsdate): New algorithm. No need to call
1998 maketime() any longer.
1999 Thanks to Paul Eggert <eggert@twinsun.com> for this change.
2001 * src/patchlevel.h: Increased patch level to "2".
2003 * src/subr.c (isdir, islink): Changed to compare stat mode bits
2006 * src/tag.c (tag_file): Added support for following symbolic links
2007 that are in the master source repository when tagging. Made tag
2008 somewhat quieter in certain cases.
2010 * src/update.c (update_process_lists): Unlink the user's file if it
2011 was put on the Wlist, meaning that the user's file is not modified
2012 and its RCS file has been removed by someone else.
2014 * src/update.c (update): Support for "cvs update dir" to correctly
2015 just update the argument directory "dir".
2017 * src/cvs.h: Fixes for RCS 5.5 parsing.
2018 * src/version_number.c (Version_Number): Fixes for parsing RCS 5.5
2019 and older RCS-format files.
2020 Thanks to Paul Eggert <eggert@twinsun.com> for these changes.
2022 * src/version_number.c (Version_Number): Bug fixes for "-f" option.
2023 Bug fixes for parsing with certain branch numbers. RCS
2024 revision/symbol parsing is much more solid now.
2026 Wed Feb 14 10:01:33 1990 Brian Berliner (berliner at sun.com)
2028 * Changes from CVS 1.0 Patchlevel 0 to CVS 1.0 Patchlevel 1; also
2029 known as "Changes from CVS 1.0 to CVS 1.1".
2031 * src/patch.c (get_rcsdate): Portability fix. Replaced call to
2032 timelocal() with call to maketime().
2034 Mon Nov 19 23:15:11 1990 Brian Berliner (berliner at prisma.com)
2036 * Sent CVS 1.0 release to comp.sources.unix moderator and FSF.
2038 * Special thanks to Dick Grune <dick@cs.vu.nl> for his work on the
2039 1986 version of CVS and making it available to the world. Dick's
2040 version is available on uunet.uu.net in the
2041 comp.sources.unix/volume6/cvs directory.
projects / dragonfly.git / blob