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

Re: CVS -> Subversion

From: David Weintraub <qazwart_at_gmail.com>
Date: Fri, 30 Jan 2009 09:39:20 -0500

I created a Perl script that went through each CVS file and deleted
the tags I didn't want to keep. Then, I ran the cvs2svn tool on the
purified CVS repository.

You have to be more careful doing this with branches. Deleting the
branch's tag will cause problems if you haven't removed the parts of
the RCS file that refer to the older branches. I skipped over the tag
if it was related to a branch.

Be careful about the cvs2svn:cvs-tag property! It gives you a great
way to refer back to the CVS repository, but you have to do one last
checkout, remove that property from each file and then another commit.
Otherwise, new revisions of your files will contain the old
cvs2svn:cvs-tag property from the previous revision.

On Thu, Jan 29, 2009 at 11:05 AM, Weichselbaumer Michael (MWE 4170)
<michael.weichselbaumer_at_ntswincash.com> wrote:
> Hello everybody,
> My company currently considers to migrate from CVS to Subversion and I have
> been fiddling around
> with cvs2svn and refinecvs a little bit.
> In our CVS repository, there a lot of tags & branches, but we would like to
> keep only a few of them.
> I have tried to accomplish this using cvs2svn, but the repositories I end up
> with after conversion are pretty messed up.
> Our repository looks like this:
> - HEAD
> - project1
> - project2
> - project3
> - ...
> - tags
> - tag1
> - tag2
> - tag3
> - ...
> - branches
> - branch1
> - branch2
> - branch3
> - ...
> the tags & branches do not contain every project in HEAD, but only some.
> What is the best way to convert to Subversion without losing the history?!
> Regards

David Weintraub
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-30 15:42:35 CET

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.