Changes 1.12.13:
SECURITY FIXES
* CVS now uses version 1.2.3 of the ZLib compression libraries in order to
avoid two recently announced security vulnerabilities in them. Both may be
used for denial of service attacks and one may reportedly allow execution of
arbitrary code, though this is not confirmed.
NEW FEATURES
* Thanks to Conrad Pino <conrad@pino.com>, a hang in the Windows client, which
had pretty much rendered the client useless, has been fixed.
* A minor problem preventing build of the Kerberos4 client has been fixed.
* The path to the config file may be set as an argument to the CVS server
commands.
* Sections of directives specific to one or more repositories and not others
may now be specified in the config file.
* %{sV} format strings are now available to the verifymsg trigger, similar to
the %{stVv} available to loginfo.
* `cvs watch add' on an empty directory no longer clears watchers, and
specifying a directory for `cvs watch add' now (correctly) sets default
attributes.
* Missing CVSROOT/history files will now cause CVS to attempt to create one.
To suppress history logging, set LogHistory equal to the empty string in
CVSROOT/config.
* There are several new options available in CVSROOT/config. These are
TmpDir, HistoryLogPath, HistorySearchPath, MinCompressionLevel, &
MaxCompressionLevel. Please see the manual for more.
* CVS on Solaris 10 was refusing to parse command options. This has been
fixed.
* The Windows client now creates locks compatible with older versions of CVS by
default. This should only be relevant if your client is accessing a local
repository concurrently with another, older client. If you would like to
disable compatibility mode (because it is slightly faster), edit the
LOCK_COMPATIBILITY flag in windows-NT/config.h and recompile.
* Misc efficiency and portability improvements.
BUG FIXES
* Thanks to Serguei E. Leontiev <lse@CryptoPro.ru>, CVS with Kerberos 5 GSSAPI
should automatically link on FreeBSD 5.x.
* Thanks to Rahul Bhargava <rahul@wandisco.com>, heavily loaded systems
suffering from a disk crash or power failure will not lose data they claimed
to have committed.
* CVS server now handles conflict markers in Entry requests as documented.
* CVS now remembers that binary file merge conflicts occurred until the
timestamp of the updated binary file changes.
* CVS client now saves some bandwidth by not sending the contents of files
with conflicts to the server when it isn't needed.
* CVS now does correct locking during import.
* A problem where the server could block indefinitely waiting for an EOF from
the client when compression was enabled has been fixed.
* `cvs diff' no longer splits its arguments on spaces.
* Thanks to an old report and patch from Stewart Brodie <stewart@eh.org>, a
potential crash in response to a corrupt RCS file has been fixed.
* CVS now locks the history and val-tags files before writing to them.
Especially with large repositories, users should no longer see new warnings
about corrupt history records when using the `cvs history' command. Existing
corrupt history records will still need to be removed manually. val-tags
corruption should have had less obvious effects, but removing the
CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to
regenerate it may eliminate a few odd behaviors and possibly cause a slight
speed up of read transactions in large repositories over time.
BUILD ISSUES
* The RPM spec file works again with the most modern versions of `rpm'. It
also finds the correct version of install-sh when building the CVS with
GSSAPI.
DEVELOPER ISSUES
* We've standardized on Automake 1.9.6 to get some at new features that make
our jobs easier. See the HACKING file for more on using the autotools with
CVS.
2013-10-14 08:51:02 +02:00
|
|
|
@comment $NetBSD: PLIST,v 1.3 2013/10/14 06:51:02 adam Exp $
|
1997-12-10 01:05:43 +01:00
|
|
|
bin/cvs
|
|
|
|
|
bin/cvsbug
|
|
|
|
|
bin/rcs2log
|
2006-03-30 05:44:41 +02:00
|
|
|
info/cvs.info
|
|
|
|
|
info/cvsclient.info
|
Update to 1.11. Changes since 1.10:
* The new "cvs version" command gives a short version message. If
the repository is remote, both the client and server versions are
reported.
* "cvs admin -t" now works correctly in client/server mode.
* The "cvs history" command output format has changed -- the date
now includes the year and is given is ISO 8601 format (yyyy-mm-dd).
Also, the new LogHistory option in CVSROOT/config can be used to
control what information gets recorded in the log file and code has
been added to record file removals.
* The buggy PreservePermissions code has been disabled.
* Anonymous read-only access can now be done without requiring a
password. On the server side, simply give that user (presumably
`anonymous') an empty password in the CVSROOT/passwd file, and then
any received password will authenticate successfully.
* There is a new access method :fork: which is similar to :local:
except that it is implemented via the CVS remote protocol, and thus
has a somewhat different set of quirks and bugs.
* The -d command line option no longer updates the CVS/Root file. For
one thing, the CVS 1.9/1.10 behavior never had updated CVS/Root in
subdirectories, and for another, it didn't seem that popular in
general. So this change restores the CVS 1.8 behavior (which is also
the CVS 1.9/1.10 behavior if the environment variable
CVS_IGNORE_REMOTE_ROOT is set; with this change,
CVS_IGNORE_REMOTE_ROOT no longer has any effect).
* It is now possible for a single CVS command to recurse into several
CVS roots. This includes roots which are located on several servers,
or which are both remote and local. CVS will make connections to as
many servers as necessary.
* It is now possible to put the CVS lock files in a directory
set by the new LockDir option in CVSROOT/config. The default
continues to be to put the lock files in the repository itself.
2000-10-18 05:31:15 +02:00
|
|
|
man/man1/cvs.1
|
|
|
|
|
man/man5/cvs.5
|
|
|
|
|
man/man8/cvsbug.8
|
1998-08-21 21:06:51 +02:00
|
|
|
share/cvs/contrib/README
|
|
|
|
|
share/cvs/contrib/clmerge
|
|
|
|
|
share/cvs/contrib/cln_hist
|
|
|
|
|
share/cvs/contrib/commit_prep
|
|
|
|
|
share/cvs/contrib/cvs2vendor
|
Update to 1.11. Changes since 1.10:
* The new "cvs version" command gives a short version message. If
the repository is remote, both the client and server versions are
reported.
* "cvs admin -t" now works correctly in client/server mode.
* The "cvs history" command output format has changed -- the date
now includes the year and is given is ISO 8601 format (yyyy-mm-dd).
Also, the new LogHistory option in CVSROOT/config can be used to
control what information gets recorded in the log file and code has
been added to record file removals.
* The buggy PreservePermissions code has been disabled.
* Anonymous read-only access can now be done without requiring a
password. On the server side, simply give that user (presumably
`anonymous') an empty password in the CVSROOT/passwd file, and then
any received password will authenticate successfully.
* There is a new access method :fork: which is similar to :local:
except that it is implemented via the CVS remote protocol, and thus
has a somewhat different set of quirks and bugs.
* The -d command line option no longer updates the CVS/Root file. For
one thing, the CVS 1.9/1.10 behavior never had updated CVS/Root in
subdirectories, and for another, it didn't seem that popular in
general. So this change restores the CVS 1.8 behavior (which is also
the CVS 1.9/1.10 behavior if the environment variable
CVS_IGNORE_REMOTE_ROOT is set; with this change,
CVS_IGNORE_REMOTE_ROOT no longer has any effect).
* It is now possible for a single CVS command to recurse into several
CVS roots. This includes roots which are located on several servers,
or which are both remote and local. CVS will make connections to as
many servers as necessary.
* It is now possible to put the CVS lock files in a directory
set by the new LockDir option in CVSROOT/config. The default
continues to be to put the lock files in the repository itself.
2000-10-18 05:31:15 +02:00
|
|
|
share/cvs/contrib/cvs_acls
|
Update cvs to 1.11.2. Changes:
Changes since 1.11.1p1:
* The "log" and "rlog" commands now have a -S option to suppress the
header information when no revisions are selected.
* A serious error that allowed read-only users to tag files has been
corrected.
* The "annotate" command will no longer annotate binary files unless
you specify the new -F option.
* The "tag" and "rtag" commands will no longer move or delete branch
tags unless you use the new -B option. (This prevents accidental
changes to branch tags that are hard to undo.)
* We've standardized on the 1.5 Automake release for the moment. Again, this
should only really affect developers. See the section of the INSTALL file
about using the autotools if you are compiling CVS yourself.
Changes from 1.11.1 to 1.11.1p1:
* Read only access was broken - now fixed.
Changes from 1.11 to 1.11.1:
* The "cvs diff" command now accepts the -y/--side=by-side and -T/
--initial-tab options. (To use these options with a remote repository,
both the client and the server must support them.)
* The expansion of the loginfo format string has changed slightly.
Previously, the expansion was surrounded by single quotes ('); if a file
name contained a single quote character, the string would not be parsed
as a single entity by the Unix shell (and it would not be possible to
parse it unambiguously). Now the expansion is surrounded by double
quotes (") and any embedded dollar signs ($), backticks (`), backslashes
(\), and double quotes are preceded by a backslash. This is parsed as a
single entity by the shell reguardless of content. This change should
not be noticable unless you're not using a Unix shell or you have
embedded the format string inside a double quoted string.
* There was a bug in the diff code which sometimes caused conflicts to
be flagged which shouldn't have been. This has been fixed.
* New "cvs rlog" and "cvs rannotate" commands have been added to get log
messages and annotations without having to have a checked-out copy.
* Exclusive revision ranges have been added to "cvs log" using ::
(similar to "cvs admin -o").
* The VMS client now accepts wildcards if you're running VMS 7.x.
* ZLIB has been updated to version 1.1.3, the most current version. This
includes mostly some optimizations and minor bug fixes.
* The ~/.cvspass file has a slightly modified format. CVSROOTs are now
stored in a new canonical form - hostnames are now case insensitive and
port numbers are always stored in the new format. Until a new login for
a particular CVSROOT is performed with the new version of CVS, new and
old versions of CVS should interoperate invisibly. After that point, an
extra login using the old version of CVS may be necessary to continue to
allow the new and old versions of CVS to interoperate using the same
~/.cvspass file and CVSROOT. The exception to this rule occurs when the
CVSROOTs used with the different versions use case insensitively
different hostnames, for example, "empress", and "empress.2-wit.com".
* A password and a port number may now be specified in CVSROOT for
pserver connections. The new format is:
:pserver:[[user][:password]@]host[:[port]]/path
Note that passwords specified in a checkout command will be saved in the
clear in the CVS/Root file in each created directory, so this is not
recommended, except perhaps when accessing anonymous repositories or the
like.
* The distribution has been converted to use Automake. This shouldn't
affect most users except to ease some portability concerns, but if you
are building from the repository and encounter problems with the
makefiles, you might try running ./noautomake.sh after a fresh update
-AC.
2002-11-24 22:31:20 +01:00
|
|
|
share/cvs/contrib/debug_check_log
|
1998-08-21 21:06:51 +02:00
|
|
|
share/cvs/contrib/intro.doc
|
|
|
|
|
share/cvs/contrib/log
|
|
|
|
|
share/cvs/contrib/log_accum
|
|
|
|
|
share/cvs/contrib/mfpipe
|
Changes 1.12.13:
SECURITY FIXES
* CVS now uses version 1.2.3 of the ZLib compression libraries in order to
avoid two recently announced security vulnerabilities in them. Both may be
used for denial of service attacks and one may reportedly allow execution of
arbitrary code, though this is not confirmed.
NEW FEATURES
* Thanks to Conrad Pino <conrad@pino.com>, a hang in the Windows client, which
had pretty much rendered the client useless, has been fixed.
* A minor problem preventing build of the Kerberos4 client has been fixed.
* The path to the config file may be set as an argument to the CVS server
commands.
* Sections of directives specific to one or more repositories and not others
may now be specified in the config file.
* %{sV} format strings are now available to the verifymsg trigger, similar to
the %{stVv} available to loginfo.
* `cvs watch add' on an empty directory no longer clears watchers, and
specifying a directory for `cvs watch add' now (correctly) sets default
attributes.
* Missing CVSROOT/history files will now cause CVS to attempt to create one.
To suppress history logging, set LogHistory equal to the empty string in
CVSROOT/config.
* There are several new options available in CVSROOT/config. These are
TmpDir, HistoryLogPath, HistorySearchPath, MinCompressionLevel, &
MaxCompressionLevel. Please see the manual for more.
* CVS on Solaris 10 was refusing to parse command options. This has been
fixed.
* The Windows client now creates locks compatible with older versions of CVS by
default. This should only be relevant if your client is accessing a local
repository concurrently with another, older client. If you would like to
disable compatibility mode (because it is slightly faster), edit the
LOCK_COMPATIBILITY flag in windows-NT/config.h and recompile.
* Misc efficiency and portability improvements.
BUG FIXES
* Thanks to Serguei E. Leontiev <lse@CryptoPro.ru>, CVS with Kerberos 5 GSSAPI
should automatically link on FreeBSD 5.x.
* Thanks to Rahul Bhargava <rahul@wandisco.com>, heavily loaded systems
suffering from a disk crash or power failure will not lose data they claimed
to have committed.
* CVS server now handles conflict markers in Entry requests as documented.
* CVS now remembers that binary file merge conflicts occurred until the
timestamp of the updated binary file changes.
* CVS client now saves some bandwidth by not sending the contents of files
with conflicts to the server when it isn't needed.
* CVS now does correct locking during import.
* A problem where the server could block indefinitely waiting for an EOF from
the client when compression was enabled has been fixed.
* `cvs diff' no longer splits its arguments on spaces.
* Thanks to an old report and patch from Stewart Brodie <stewart@eh.org>, a
potential crash in response to a corrupt RCS file has been fixed.
* CVS now locks the history and val-tags files before writing to them.
Especially with large repositories, users should no longer see new warnings
about corrupt history records when using the `cvs history' command. Existing
corrupt history records will still need to be removed manually. val-tags
corruption should have had less obvious effects, but removing the
CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to
regenerate it may eliminate a few odd behaviors and possibly cause a slight
speed up of read transactions in large repositories over time.
BUILD ISSUES
* The RPM spec file works again with the most modern versions of `rpm'. It
also finds the correct version of install-sh when building the CVS with
GSSAPI.
DEVELOPER ISSUES
* We've standardized on Automake 1.9.6 to get some at new features that make
our jobs easier. See the HACKING file for more on using the autotools with
CVS.
2013-10-14 08:51:02 +02:00
|
|
|
share/cvs/contrib/newcvsroot
|
Update cvs to 1.11.2. Changes:
Changes since 1.11.1p1:
* The "log" and "rlog" commands now have a -S option to suppress the
header information when no revisions are selected.
* A serious error that allowed read-only users to tag files has been
corrected.
* The "annotate" command will no longer annotate binary files unless
you specify the new -F option.
* The "tag" and "rtag" commands will no longer move or delete branch
tags unless you use the new -B option. (This prevents accidental
changes to branch tags that are hard to undo.)
* We've standardized on the 1.5 Automake release for the moment. Again, this
should only really affect developers. See the section of the INSTALL file
about using the autotools if you are compiling CVS yourself.
Changes from 1.11.1 to 1.11.1p1:
* Read only access was broken - now fixed.
Changes from 1.11 to 1.11.1:
* The "cvs diff" command now accepts the -y/--side=by-side and -T/
--initial-tab options. (To use these options with a remote repository,
both the client and the server must support them.)
* The expansion of the loginfo format string has changed slightly.
Previously, the expansion was surrounded by single quotes ('); if a file
name contained a single quote character, the string would not be parsed
as a single entity by the Unix shell (and it would not be possible to
parse it unambiguously). Now the expansion is surrounded by double
quotes (") and any embedded dollar signs ($), backticks (`), backslashes
(\), and double quotes are preceded by a backslash. This is parsed as a
single entity by the shell reguardless of content. This change should
not be noticable unless you're not using a Unix shell or you have
embedded the format string inside a double quoted string.
* There was a bug in the diff code which sometimes caused conflicts to
be flagged which shouldn't have been. This has been fixed.
* New "cvs rlog" and "cvs rannotate" commands have been added to get log
messages and annotations without having to have a checked-out copy.
* Exclusive revision ranges have been added to "cvs log" using ::
(similar to "cvs admin -o").
* The VMS client now accepts wildcards if you're running VMS 7.x.
* ZLIB has been updated to version 1.1.3, the most current version. This
includes mostly some optimizations and minor bug fixes.
* The ~/.cvspass file has a slightly modified format. CVSROOTs are now
stored in a new canonical form - hostnames are now case insensitive and
port numbers are always stored in the new format. Until a new login for
a particular CVSROOT is performed with the new version of CVS, new and
old versions of CVS should interoperate invisibly. After that point, an
extra login using the old version of CVS may be necessary to continue to
allow the new and old versions of CVS to interoperate using the same
~/.cvspass file and CVSROOT. The exception to this rule occurs when the
CVSROOTs used with the different versions use case insensitively
different hostnames, for example, "empress", and "empress.2-wit.com".
* A password and a port number may now be specified in CVSROOT for
pserver connections. The new format is:
:pserver:[[user][:password]@]host[:[port]]/path
Note that passwords specified in a checkout command will be saved in the
clear in the CVS/Root file in each created directory, so this is not
recommended, except perhaps when accessing anonymous repositories or the
like.
* The distribution has been converted to use Automake. This shouldn't
affect most users except to ease some portability concerns, but if you
are building from the repository and encounter problems with the
makefiles, you might try running ./noautomake.sh after a fresh update
-AC.
2002-11-24 22:31:20 +01:00
|
|
|
share/cvs/contrib/pvcs2rcs
|
Changes 1.12.13:
SECURITY FIXES
* CVS now uses version 1.2.3 of the ZLib compression libraries in order to
avoid two recently announced security vulnerabilities in them. Both may be
used for denial of service attacks and one may reportedly allow execution of
arbitrary code, though this is not confirmed.
NEW FEATURES
* Thanks to Conrad Pino <conrad@pino.com>, a hang in the Windows client, which
had pretty much rendered the client useless, has been fixed.
* A minor problem preventing build of the Kerberos4 client has been fixed.
* The path to the config file may be set as an argument to the CVS server
commands.
* Sections of directives specific to one or more repositories and not others
may now be specified in the config file.
* %{sV} format strings are now available to the verifymsg trigger, similar to
the %{stVv} available to loginfo.
* `cvs watch add' on an empty directory no longer clears watchers, and
specifying a directory for `cvs watch add' now (correctly) sets default
attributes.
* Missing CVSROOT/history files will now cause CVS to attempt to create one.
To suppress history logging, set LogHistory equal to the empty string in
CVSROOT/config.
* There are several new options available in CVSROOT/config. These are
TmpDir, HistoryLogPath, HistorySearchPath, MinCompressionLevel, &
MaxCompressionLevel. Please see the manual for more.
* CVS on Solaris 10 was refusing to parse command options. This has been
fixed.
* The Windows client now creates locks compatible with older versions of CVS by
default. This should only be relevant if your client is accessing a local
repository concurrently with another, older client. If you would like to
disable compatibility mode (because it is slightly faster), edit the
LOCK_COMPATIBILITY flag in windows-NT/config.h and recompile.
* Misc efficiency and portability improvements.
BUG FIXES
* Thanks to Serguei E. Leontiev <lse@CryptoPro.ru>, CVS with Kerberos 5 GSSAPI
should automatically link on FreeBSD 5.x.
* Thanks to Rahul Bhargava <rahul@wandisco.com>, heavily loaded systems
suffering from a disk crash or power failure will not lose data they claimed
to have committed.
* CVS server now handles conflict markers in Entry requests as documented.
* CVS now remembers that binary file merge conflicts occurred until the
timestamp of the updated binary file changes.
* CVS client now saves some bandwidth by not sending the contents of files
with conflicts to the server when it isn't needed.
* CVS now does correct locking during import.
* A problem where the server could block indefinitely waiting for an EOF from
the client when compression was enabled has been fixed.
* `cvs diff' no longer splits its arguments on spaces.
* Thanks to an old report and patch from Stewart Brodie <stewart@eh.org>, a
potential crash in response to a corrupt RCS file has been fixed.
* CVS now locks the history and val-tags files before writing to them.
Especially with large repositories, users should no longer see new warnings
about corrupt history records when using the `cvs history' command. Existing
corrupt history records will still need to be removed manually. val-tags
corruption should have had less obvious effects, but removing the
CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to
regenerate it may eliminate a few odd behaviors and possibly cause a slight
speed up of read transactions in large repositories over time.
BUILD ISSUES
* The RPM spec file works again with the most modern versions of `rpm'. It
also finds the correct version of install-sh when building the CVS with
GSSAPI.
DEVELOPER ISSUES
* We've standardized on Automake 1.9.6 to get some at new features that make
our jobs easier. See the HACKING file for more on using the autotools with
CVS.
2013-10-14 08:51:02 +02:00
|
|
|
share/cvs/contrib/rcs-5.7-commitid.patch
|
1998-08-21 21:06:51 +02:00
|
|
|
share/cvs/contrib/rcs-to-cvs
|
|
|
|
|
share/cvs/contrib/rcs2log
|
|
|
|
|
share/cvs/contrib/rcslock
|
Changes 1.12.13:
SECURITY FIXES
* CVS now uses version 1.2.3 of the ZLib compression libraries in order to
avoid two recently announced security vulnerabilities in them. Both may be
used for denial of service attacks and one may reportedly allow execution of
arbitrary code, though this is not confirmed.
NEW FEATURES
* Thanks to Conrad Pino <conrad@pino.com>, a hang in the Windows client, which
had pretty much rendered the client useless, has been fixed.
* A minor problem preventing build of the Kerberos4 client has been fixed.
* The path to the config file may be set as an argument to the CVS server
commands.
* Sections of directives specific to one or more repositories and not others
may now be specified in the config file.
* %{sV} format strings are now available to the verifymsg trigger, similar to
the %{stVv} available to loginfo.
* `cvs watch add' on an empty directory no longer clears watchers, and
specifying a directory for `cvs watch add' now (correctly) sets default
attributes.
* Missing CVSROOT/history files will now cause CVS to attempt to create one.
To suppress history logging, set LogHistory equal to the empty string in
CVSROOT/config.
* There are several new options available in CVSROOT/config. These are
TmpDir, HistoryLogPath, HistorySearchPath, MinCompressionLevel, &
MaxCompressionLevel. Please see the manual for more.
* CVS on Solaris 10 was refusing to parse command options. This has been
fixed.
* The Windows client now creates locks compatible with older versions of CVS by
default. This should only be relevant if your client is accessing a local
repository concurrently with another, older client. If you would like to
disable compatibility mode (because it is slightly faster), edit the
LOCK_COMPATIBILITY flag in windows-NT/config.h and recompile.
* Misc efficiency and portability improvements.
BUG FIXES
* Thanks to Serguei E. Leontiev <lse@CryptoPro.ru>, CVS with Kerberos 5 GSSAPI
should automatically link on FreeBSD 5.x.
* Thanks to Rahul Bhargava <rahul@wandisco.com>, heavily loaded systems
suffering from a disk crash or power failure will not lose data they claimed
to have committed.
* CVS server now handles conflict markers in Entry requests as documented.
* CVS now remembers that binary file merge conflicts occurred until the
timestamp of the updated binary file changes.
* CVS client now saves some bandwidth by not sending the contents of files
with conflicts to the server when it isn't needed.
* CVS now does correct locking during import.
* A problem where the server could block indefinitely waiting for an EOF from
the client when compression was enabled has been fixed.
* `cvs diff' no longer splits its arguments on spaces.
* Thanks to an old report and patch from Stewart Brodie <stewart@eh.org>, a
potential crash in response to a corrupt RCS file has been fixed.
* CVS now locks the history and val-tags files before writing to them.
Especially with large repositories, users should no longer see new warnings
about corrupt history records when using the `cvs history' command. Existing
corrupt history records will still need to be removed manually. val-tags
corruption should have had less obvious effects, but removing the
CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to
regenerate it may eliminate a few odd behaviors and possibly cause a slight
speed up of read transactions in large repositories over time.
BUILD ISSUES
* The RPM spec file works again with the most modern versions of `rpm'. It
also finds the correct version of install-sh when building the CVS with
GSSAPI.
DEVELOPER ISSUES
* We've standardized on Automake 1.9.6 to get some at new features that make
our jobs easier. See the HACKING file for more on using the autotools with
CVS.
2013-10-14 08:51:02 +02:00
|
|
|
share/cvs/contrib/sandbox_status
|
1998-08-21 21:06:51 +02:00
|
|
|
share/cvs/contrib/sccs2rcs
|
Changes 1.12.13:
SECURITY FIXES
* CVS now uses version 1.2.3 of the ZLib compression libraries in order to
avoid two recently announced security vulnerabilities in them. Both may be
used for denial of service attacks and one may reportedly allow execution of
arbitrary code, though this is not confirmed.
NEW FEATURES
* Thanks to Conrad Pino <conrad@pino.com>, a hang in the Windows client, which
had pretty much rendered the client useless, has been fixed.
* A minor problem preventing build of the Kerberos4 client has been fixed.
* The path to the config file may be set as an argument to the CVS server
commands.
* Sections of directives specific to one or more repositories and not others
may now be specified in the config file.
* %{sV} format strings are now available to the verifymsg trigger, similar to
the %{stVv} available to loginfo.
* `cvs watch add' on an empty directory no longer clears watchers, and
specifying a directory for `cvs watch add' now (correctly) sets default
attributes.
* Missing CVSROOT/history files will now cause CVS to attempt to create one.
To suppress history logging, set LogHistory equal to the empty string in
CVSROOT/config.
* There are several new options available in CVSROOT/config. These are
TmpDir, HistoryLogPath, HistorySearchPath, MinCompressionLevel, &
MaxCompressionLevel. Please see the manual for more.
* CVS on Solaris 10 was refusing to parse command options. This has been
fixed.
* The Windows client now creates locks compatible with older versions of CVS by
default. This should only be relevant if your client is accessing a local
repository concurrently with another, older client. If you would like to
disable compatibility mode (because it is slightly faster), edit the
LOCK_COMPATIBILITY flag in windows-NT/config.h and recompile.
* Misc efficiency and portability improvements.
BUG FIXES
* Thanks to Serguei E. Leontiev <lse@CryptoPro.ru>, CVS with Kerberos 5 GSSAPI
should automatically link on FreeBSD 5.x.
* Thanks to Rahul Bhargava <rahul@wandisco.com>, heavily loaded systems
suffering from a disk crash or power failure will not lose data they claimed
to have committed.
* CVS server now handles conflict markers in Entry requests as documented.
* CVS now remembers that binary file merge conflicts occurred until the
timestamp of the updated binary file changes.
* CVS client now saves some bandwidth by not sending the contents of files
with conflicts to the server when it isn't needed.
* CVS now does correct locking during import.
* A problem where the server could block indefinitely waiting for an EOF from
the client when compression was enabled has been fixed.
* `cvs diff' no longer splits its arguments on spaces.
* Thanks to an old report and patch from Stewart Brodie <stewart@eh.org>, a
potential crash in response to a corrupt RCS file has been fixed.
* CVS now locks the history and val-tags files before writing to them.
Especially with large repositories, users should no longer see new warnings
about corrupt history records when using the `cvs history' command. Existing
corrupt history records will still need to be removed manually. val-tags
corruption should have had less obvious effects, but removing the
CVSROOT/val-tags file and allowing a 1.11.21 or later version of CVS to
regenerate it may eliminate a few odd behaviors and possibly cause a slight
speed up of read transactions in large repositories over time.
BUILD ISSUES
* The RPM spec file works again with the most modern versions of `rpm'. It
also finds the correct version of install-sh when building the CVS with
GSSAPI.
DEVELOPER ISSUES
* We've standardized on Automake 1.9.6 to get some at new features that make
our jobs easier. See the HACKING file for more on using the autotools with
CVS.
2013-10-14 08:51:02 +02:00
|
|
|
share/cvs/contrib/validate_repo
|
