[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Upgrading cvs from 1.11.21 to 1.12.13

From: Mark D. Baushke
Subject: Re: Upgrading cvs from 1.11.21 to 1.12.13
Date: Tue, 21 Mar 2006 09:01:02 -0800

Hash: SHA1

Zanabria, Moises <address@hidden> writes:

> Guys,
> Besides the News at
> =text/vnd.viewcvs-markup 
> Do you have a features compare table, where I can see all the features
> in 1.12.xx over 1.11.x ?

I am not aware of any. If someone wants to write up such a comparison,
it might be useful to add it to the documentation.

> Is there any risk upgrading our cvs binaries from cvs 1.11.21 to
> 1.12.13 ?

You may find it desirable to update how you are using the various CVS
commit triggers. It will work fine, but generate some warnings until
you update the commit files.

> Server/Client should same version level?

This is not required. We do recommend using the latest revisions
of CVS for the most part as that gets you away from known bugs.

> Or clients can work using 1.11.x?

Sure. I have a few places where I am using 1.12.x server and a 1.11.x
client and a few other places where I am using the reverse. They
interoperate fine.

> WinCVS/CVSNT clients works well with 1.12.X cvs server?

The seem to work okay as far as I can tell, but I have seen very little
in the way of WinCVS/CVSNT client usage for myself.

I seem to recall that SmartCVS clients had some problems with some cvs
1.12.x server regarding compression. The workaround was to change the -z0
option to disable it for the time being.

> Thanks in advance for any advise.
> Moises.

        Good luck,
        -- Mark
Version: GnuPG v1.4.2.2 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]