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

Suggestions for CVS->SVN Migration

From: Andrew Norman <Andrew.Norman_at_erudine.com>
Date: 2006-12-20 15:38:16 CET

I have recently migrated a CVS repository to SVN. Now this was the first
pass at the solution and I am not sure that I am doing it the right way
or the suggested layout to make support/branching and working with the
system easier. So I have decided to ask the enlightened people on this
list for some wisdom.
Current Layout:
CVS (Around 60 Eclipse projects):
SVN (Migrated: Approach One)
1/ The Customer set of projects don't have any branches/tags at the
2/ The Toolkit Projects are desired to be in two separate groups but the
commits/version numbers are the same due to the close coupling between
the projects.
3/ The major aim of the migration is the use of atomic commits across
the various projects as we have been having problems with partial CVS
commits across the projects colliding.
Now each of the projects in the SVN are checked out to appear the same
as the initial CVS projects when working in Eclipse. Currently we are
having problems merging and seem to lose files (I think half of this is
probably education of the developers using the subversive plug-in).
What I am looking at is a major refactor of the repository to make the
conversion into Subversion easier to maintain in the long run. Because
currently I am feeling like the current solution is not going to be able
to be maintained for a long time as projects come and go during the
course of normal development.
Received on Wed Dec 20 15:41:29 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.