Kenneth Porter wrote:
On Wednesday, February 07, 2007 11:56 AM +0000 Jonathan Perret
<[EMAIL PROTECTED]> wrote:
Perhaps the vss2svn wiki should contain information of this kind ?
Sounds like a good idea.
I did something like that, but my conversion was on a Linux box. I
didn't have access to the customer's VSS server to install software,
so I installed cwrsync (a Windows rsync client/server) on a convenient
machine at the customer site that had access to the VSS DB. I
configured it as a read-only rsync server, and used the rsync client
on my Linux box at my own site to keep my local copy of the VSS DB up
to date for each attempt.
Thanks Jonathan for your detailed workflow. My only concern is that I
don't want to give the impression that VSS or any other software is
*required*. As Kenneth mentioned he performed the migration without even
access to a Windows box. I do think it is very helpful to have one or
more "use cases" that people can refer to. It seems that different
people will often have very different issues that they face so there
will not be any single recipe that works for everyone.
toby
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
