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

RE: RE: CVS / Subversion interoperability

From: <Chris.Fouts_at_qimonda.com>
Date: 2006-12-21 20:02:15 CET

this will be an interesting experiment!

________________________________

        From: Rob van Oostrum [mailto:rob.vanoostrum@blastradius.com]
        Sent: Thursday, December 21, 2006 1:45 PM
        To: Steven Whatmore; subversion users
        Subject: RE: CVS / Subversion interoperability
        
        

        Haven't tried this myself ... but ... you could try and
svn:ignore the CVS 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
Received on Thu Dec 21 20:11:04 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.