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

FW: Re: CVS / Subversion interoperability

From: Steven Whatmore <Stevenw_at_sigmasoft.ca>
Date: 2006-12-27 17:18:16 CET

Season's Greetings

As per the original post, I am planning on using CVS as the master until
I am confident that everything with Subversion is setup properly,
functioning as expected and all of the operational items have been taken
of (ie. BACKUP). Since we have been using CVS for a while all of these
items have already been taken care of, and thus the original intention
behind the post.

Since, our first "Subversion" project is going to going to be a small
team, I (meaning me personally) plan on manually maintaining the project
source in both repositories, but wanted to streamline this as much as
possible, using Subversion for daily development activities and then
checking in the updated source into CVS at the end of the day.

Your solution is pretty much what I expected but just wanted to see if
anyone else had tried this approach.

Thanks for response.


-----Original Message-----
From: Robert Swarbrick [mailto:robert@wombatfs.com]
Sent: Friday, December 22, 2006 10:29 AM
Cc: subversion users
Subject: Re: CVS / Subversion interoperability

I have this working as an initial experiment on my system. Which is fine

for my personal use, but persuading a team to remember to commit to both

repositories at the same time will be awkward.

Getting the initial directory involved having both checked out into two
separate directories, then physically copying one directory tree on top
of the other - I couldn't find any other way of persuading either
Subversion or CVS to do a checkout (to create the CVS / .svn
directories) when there was already a bunch of files and directories
existing - "in the way".


Rob van Oostrum wrote:
> Haven't tried this myself ... but ... you could try and svn:ignore the
> dirs, and .cvsignore the .svn dirs. That **might** work. You can use
> cvs2svn to do the initial migration and ignore/exclude the CVS dirs in

> the process.
> Good luck
> R.
> * From: * Steven Whatmore [mailto:Stevenw@sigmasoft.ca]
> *Sent:* Thursday, December 21, 2006 1:41 PM
> *To:* subversion users
> *Subject:* CVS / Subversion interoperability
> Good afternoon,
> I am about to perform a migration to Subversion from CVS and until the

> system has been stabilized (operationalized, backup procedures etc
> etc), I would like to maintain my source code projects in both CVS &
> Subversion.
> Is this possible, in that I can have the same project folder (locally)

> managed by both CVS & Subversion, or do the control files or something

> else conflict with one another?
> I am using Eclipse as my IDE locally, and would like to make my codes
> changes and then check those changes into both my new Subversion
> repository and my current CVS repository.
> * Steve Whatmore *
> Technical Lead Web Development
> Sigma Software Solutions

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 27 17:18:32 2006

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.