[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: converting from SVN to CVS

From: Kenneth Goldman <kgoldman_at_us.ibm.com>
Date: Fri, 23 Jan 2009 09:35:56 -0500

"Robert P. J. Day" <rpjday_at_crashcourse.ca> wrote on 01/23/2009 05:46:47 AM:

> most people on this list are technically adept with subversion.
> where's the marketing? where's the ammunition that jeremy could take
> into a meeting with his new bosses?

As a long time CVS user who recently had to move to SVN, I propose:


- The main reason for the migration was that CVS required everyone
to have user accounts on the CVS server, which compromised security.
SVN does not.

- Atomic check in with automatic tagging

Minuses (please don't shoot the messenger):

- Documentation. The CVS manual tells you how to do tasks. The SVN
manual gives you SVN theory from which you can eventually figure
out how to do tasks.

- Integration with other tools. E.g., CVS with emacs just works.
Integrating SVN is a project.

- Newline conversion for Windows is automatic and cannot easily
be turned off.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-23 17:08:09 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.