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


From: Georg Viehöver <viehoever_at_sigma-c.de>
Date: 2005-05-11 16:51:00 CEST

We tried to do that using vss2svn, which in general works fine. However, there are certain features in VSS that are not easily transfered to SVN (such as links or cloaked modules), so in the end we decided to do a migration with a flat file structure (without history). On this occasion, we also did a general cleanup of sources etc.. Product support for old versions is done in VSS (for a while), new development for the next major releases is done in subversion.
Note that use of subversion with visual studio is not necesarilly faster than VSS. VS and VSS are well integrated and relatively fast. VSS, svn_proxy (pushok.com) and subversion are rather slow. The pure svn commandline client or TortoiseSvn on Windows is fine. We use FreeBSD as a subversion server.


Von: Markus Karg [mailto:markus.karg@quipsy.de]
Gesendet: Mittwoch, 11. Mai 2005 12:21
An: users@subversion.tigris.org
Betreff: MS VSS to SVN

We want to move from VSS to SVN. Has anybody experience with this? Is there something special to notice? Are there tools for moving our project history from VSS to SVN?
Mit freundlichem Gruss / With kind regards
Markus KARG, Staatl. gepr. Inf.
Entwicklung / R & D
Received on Wed May 11 18:29:29 2005

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.