>
>
> Interesting. I'm actually using a script called "migrate.pl" that is
> for converting from vss to svn, though I've fixed a few "bugs" in it
> already. It actually commits changes one rev at a time from each file
> in vss to svn. I'll have to check to see if it is attempting to set
> this property. Thanks much for the info!
There are two different approaches to this. The one that the included
Python script does is using creates a dump log and then imports it. I
found it didn't work well for me. The "migrate.pl" I found worked
better, but after a certain amount of frustration due to numerous bugs
in it, I rewrote it from scratch. It pulls the revisions out one at a
time and commits them.
I also found it didn't set the dates correctly, and am modifying it to
do so through propset. One feature I added is that it treats consecutive
commits with the same date, user, and comment as an atomic commit in SVN
(atomic commits don't exist in VSS), which greatly lowers the amount of
migration time and falsely-inflated revision numbers.
If anyone is interested in this script, I could clean it up and post it.
It uses some in-house modules that I could just roll into one file.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 8 00:22:50 2004