[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: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Fri, 23 Jan 2009 06:39:05 -0600

On Jan 23, 2009, at 04:46, Robert P. J. Day wrote:

> On Fri, 23 Jan 2009, JeremyP wrote:
>> On 22 Jan 2009, at 22:34, Jason Boehle wrote:
>>> My company has been acquired, and we previously used SVN, but the
>>> new company uses CVS.
>> My deepest sympathies.
>> I don't know the answer to your specific question (so you can stop
>> reading now if you like), but I would resist migrating back, if I
>> were you and in fact I would do my best to convince your new masters
>> to migrate to svn rather than the other way around. Subversion is
>> far superior to CVS.
> sure it is, but if you were in jeremy's position and were asked to
> make a case for moving on up to svn, how would you do it? in most
> cases, any argument for migrating to a new piece of software will be
> met with, "but XYZ has worked for us so far, i don't see any need to
> change."

You could tell your bosses that a Subversion repository cannot be
converted back to a CVS repository while preserving history (this may
in fact be true). Of course you could "svn export" your sources and
import them into a new CVS repository and lose all the history, but
you would make the case that it would be an unacceptable detriment to
your development style to lose the history so they should let you
continue to use your tools as is. Then as time goes on you can point
out the advantages of your Subversion repository over their CVS
repositories and hopefully eventually get them to switch.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-23 17:01:00 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.