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

Questionette...

From: Steve Haeck <shaeck_at_lineone.net>
Date: 2003-12-18 12:49:06 CET

Subversion has come on leaps and bounds since I first tried it, and it has
rapidly become my version control system of choice for new projects (predominantly
on a Win32 platform) where previously (horror of horrors) MS Visual Sourcesafe
seemed the best compromise - mainly due to issues of integration with Developer
Studio. I am aware of ankhsvn, and this (in association with RapidSvn and
TortoiseSvn) promise a much improved alternative.

I would like to know if anyone else has seriously considered migrating large
scale legacy code bases to Subversion while retaining historic annotations?
It would be important not only for historic change sequences to be remain
intact, but also labels, and for there to be some way to associate previous
revision numbers with files (in case some obscure printed document or email
etc. refers to a file by version number in the old repository.

Is there already a migration tool - and, if not, is one likely to be written
any time soon? I can imagine that it would be easy to migrate from, say,
CVS or RCS - as the repository format is open... can anyone comment on the
difficulty of handling this for existing proprietary systems (specifically
Sourcesafe...)?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 18 17:15:47 2003

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.