The cvs v1_11_1 product is based on the 1.11.1 release of cvs, with
the addition of the FERMICVSUSER patch, and a patch to the gserver
code to allow :gserver:user@host:/path CVSROOT values to work [the
stock code ignores the 'user@' part, and logs you in as whatever
username corresponds to your kerberos principal].

According to the NEWS file in the cvs distribution, here are the
changes since cvs v1_10:

-----------

Changes since 1.11:

* New "cvs rlog" and "cvs rannotate" commands have been added to get log
messages and annotations without having to have a checked-out copy.

* 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 ./noautoconf.sh after a fresh update -AC.
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.