RE: How should I deal with this CVS to Subversion migration issue (and how is this done the Subversion way?)
From: Jens Schmidt <JensS_at_dyno.com.au>
Date: 2007-05-03 02:25:11 CEST
Here is what I did to convert our existing CVS to SVN using cvs2svn.
In order to run correctly (on windows!) cvs2svn requires the following
* unix tools (UnxUtils.zip + UnxUpdates.zip). You must update the path
* RCS is recommended for the conversion. You must update the path
Copy CVSROOT from old linux server into a temporary location. Open a
set path=C:\RCS\bin\win32;%path%
cvs2svn.py -v --existing-svnrepos -s c:\repository C:\Temp\cvsroot
Hope that helps
Jens
-----Original Message-----
I have a possibly nasty situation in a CVS migration to Subversion and
Note: Many parts of the development are on windows though the CVS repo
Several different teams use the same CVS repo (with little content
a. Allow a single SCM solution
The weirdness comes from the example below which shows that the CVS
cvsroot/
1. How would you achieve the same results in Subversion - Are
2. How is cvs2svn going to migrate this? Will it follow the symlinks
-- Talden --------------------------------------------------------------------- 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.orgReceived on Thu May 3 02:26:02 2007 |
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.