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

Re: Suggestions for CVS->SVN Migration

From: Michael Haggerty <mhagger_at_alum.mit.edu>
Date: 2006-12-21 10:35:51 CET

Les Mikesell wrote:
> On Wed, 2006-12-20 at 14:38 +0000, Andrew Norman wrote:
>> Current Layout:
>> CVS (Around 60 Eclipse projects):
>> Project1
>> Project2
>> Project3
>> SVN (Migrated: Approach One)
>> Toolkit/trunk/base/Project1
>> Toolkit/branches/0-0-1/base/Project1
>> Toolkit/branches/0-0-2/base/Project1
>> Toolkit/trunk/extensions/Project2
>> Toolkit/branches/0-0-1/extensions/Project2
>> Toolkit/branches/0-0-2/extensions/Project2
>> Customer/trunk/Project3
>> Note:
>> 1/ The Customer set of projects don't have any branches/tags at the
>> moment
> You probably want to cvs2svn the individual project modules separately
> so you get the branch/trunk/tags directories for each, then svnadmin
> load them with a -parent-dir argument to splice them where you want in
> the subversion repository.

As of version 1.5.0, cvs2svn supports multiproject conversions
(converting multiple subprojects, each with its own trunk/tags/branches
directories, within a single run of cvs2svn). This mode of operation is
preferred to running cvs2svn multiple times as it preserves the
chronological order of the commits across projects.

See the cvs2svn docs for details. Please note that you have to use the
--config file method of running cvs2svn to use the multiproject feature.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 21 10:37:24 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.