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

Re: Migrating from MS SourceSafe to SubVersion

From: Steve Williams <stevewilliams_at_kromestudios.com>
Date: 2004-06-18 00:43:55 CEST

> Secondly, it may be difficult to convince some people (not in our group)
to switch over. If there were any way to keep BOTH systems active and
somehow mirror changes made in each to the other system, then that would be,
in my mind, ideal. But that may be difficult or impossible to achieve. I'd
even be happy with "one-way" updates, where updates to SV automatically
trigger a checkin of that same change to SS -- it's better than nothing.

You would not be able to mirror from VSS to SVN sinve there is no server in
VSS to handle this. VSS is just sophisticated file sharing. To mirror from
SVN to VSS, you could create a post-commit hook that uses the VSS
command-line client to check out the file, replace the file with the new
file and check it in. But then there's the question of how to get the
username and password in the post-commit hook to use with the VSS check-out
and check-in. But this is really just a recipe for a whole world of pain.
Why update VSS if everyone should be using SVN? You are just tempting some
developers to "accidentally" keep using VSS.

Switch over, but keep the old VSS database for historical reasons. That is
what we plan to do.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 18 00:45:17 2004

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.