[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: Les Mikesell <lesmikesell_at_gmail.com>
Date: Wed, 28 Jan 2009 10:26:03 -0600

Bob Archer wrote:
> So, I would hope that the same thing would occur during any merger.
> Saying "we are the ones that bought you so it's our way or the highway"
> isn't good business.

That doesn't mean it can't happen, but it is worth trying anyway.

> Also, I see no reason why both systems can't be maintained. There is no
> license cost to use/keep svn. So, it is entirely possible that the svn
> system could be maintained. Converting from one system to another no
> matter if you are going from cvs->svn or vice versa is disruptive and
> time consuming.

That might be the path of least resistance since there is no tool to do
the conversion and no cost for the software. Everyone who works with
open source is already used to having multiple clients to pull from
remote repositories that use different things. You might be able to
consolidate the repositories onto the same server for easier
maintenance, though, to reduce the perceived cost. The big-picture view
may be about maintaining the critical servers with backups and backup
power in one location. If you can start with this approach, the choice
of which to abandon can be made later after some experience with both.

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