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
Rob van Oostrum wrote:
>
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 22 18:17:55 2006