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

Re: [OT] Re: VSS to SVN migration script

From: Toby Johnson <toby_at_etjohnson.us>
Date: 2004-05-21 03:39:35 CEST

Jens B. Jorgensen wrote:

> Hey guys! I'm actually the original author (plagiarist? I borrowed
> heavily from cvs2svn.py) of vss2svn.py. We took the directory approach
> because sadly (at through the automation interface) history on actual
> files is incomplete. Believe me, parsing the text of ss.exe was not
> the route of choice! I was originally trying to do it through the
> automation interface as this is much easier but alas it cannot be done.

Yes, I realized early on that VSS's "API" is very incomplete and
inadequate. It seemed everything was geared around setting up hooks for
certain events, but since VSS has no server component, you must deploy
your hook scripts to all clients who use it!

By file vs. directory approach, I meant using ss.exe to get file history
vs. directory history. I'm still using ss.exe (and trying to account for
all possible outputs it gives). I actually borrowed the methodology from
the "migrate.pl" script that's floating around, but it never worked
correctly and it was easier for me to start from scratch than try to fix it.

And yes, VSS's notion of labels seems to be rather weird; it's like
labeling a file is a separate item in its history, kinda like a commit
without actually changing anything. Plus you can have labels on
projects, and sometimes those get inherited by files in that project and
sometimes they don't. In the end, it's just not worth it to try to
migrate them.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 21 03:40:11 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.