Martin Fuchs wrote:
On 07.01.2005 10:29:59 Werner Guttmann wrote:
thank for your valuable feedback, and to some degree I agree with you. I for
myself have never seen any problems with CVS (except for teams spread across locations such as New York, London and Tokyo, where all team members
in a different location than the CVS repository suffer a performance penalty).
Well, there is one additional (minor) problem with CVS. It doesn't handle time zones correctly. After each switch to/from daylight saving time the whole source tree is pulled over the net again.
That's really a problem with the clients though, not the server, in my opinon anyway. I wrote a little command line utility that automatically adjusts the timestamp in the CVS/Entries files. I just run that once after a timezone change and it fixes the problem locally. I never have to re-pull the source tree. Since I work remotely from Texas, it would kill me to have to re-pull all the sources for all the projects I work on, so that's why I wrote the little utility to just fix the CVS/Entries files instead. Then when I run my CVS client, everything is back to normal.
--Keith
Even more, the time zone handling between different implementations is different: If one checkes out using the windows command line client, and after that updated using Wincvs or the Eclipse plugin, the same effect happens: It updates the whole source tree, though no change occured. Subversion uses standardized time zone handling routines in common libraries for all clients, so this problem doesn't occure.
Regards,
Martin
------------------------------------------------------------------------
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
