AW: CVS update to 1.11.17

[Schopper Andreas]

Thank you for the quick answer. Do I have to run the 'cvs init' on each
repository that exist? I read that it is dangerous to do this! What is
CVS doing after running that command on an existing repository?

Andreas

-----Ursprungliche Nachricht-----
Von: mdb@juniper.net [mailto:mdb@juniper.net]Im Auftrag von Mark D.
Baushke
Gesendet: Montag, 14. Juni 2004 17:47
An: Schopper Andreas
Cc: 'bug-cvs@gnu.org'
Betreff: Re: CVS update to 1.11.17 


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Schopper Andreas <aschopper@klug-is.de> writes:

> I'm using CVS 1.11 (client/server) on Suse Linux 8.0. Can I simple
> update to the latest version 1.11.17 without any problems with the
> existing repositories?

Yes.

> Are there any extensive changes?

The format of the repository remains the same.

The changes to cvs itself are not extensive, mostly bug fixes with
some additional features.

You should read the cvs-1.11.17/NEWS file for detailed changes.

A few of the CVSROOT files may give you some warnings, depending on your
configuraiton.

  - CVSROOT/modules no longer supports the -i switch (checkin_prog).

  - CVSROOT/modules no longer supports the -u switch (update_prog).

You are also going to want to run 'cvs init' to have it update some
files you are possibly missing in your CVSROOT directory.

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFAzciN3x41pRYZE/gRAqp1AJ9lgHgI9Lt8Ues+ezzEyncEH9rc9gCdGPVZ
SkQ2nndvRpKAVknPMwAwVxQ=
=jp7E
-----END PGP SIGNATURE-----