Wow, I've never had the Perl interpreter crash! I would bet it's a
memory issue, if it was still building the history. Maybe I should write
all of the comments out to temporary files instead of storing them in
memory. Since I write them out to a temporary file during the SVN import
anyway, that should be a pretty easy fix.
I'd be interested in seeing the last few lines of the debug output, but
seeing as how long it must take to run on a few hundred files, I won't
expect it anytime soon!
Steve Williams wrote:
>It crashed the Perl interpreter after getting the history of a few hundred
>files. I've started it again with the --debug option.
>
>Sly
>
>----- Original Message -----
>From: "Steve Williams" <stevewilliams@kromestudios.com>
>To: "Toby Johnson" <toby@etjohnson.us>; <users@subversion.tigris.org>
>Sent: Tuesday, May 25, 2004 5:24 PM
>Subject: Re: Update to vss2svn.pl
>
>
>
>
>>Ignoring the labels is not an issue. We have no need to migrate them.
>>
>>
>The
>
>
>>crash when it cannot find a comment as the last line of a history is still
>>there, so I just changed line 1534 to set the revision comment to "No
>>comment" instead of the script dying. It is currently processing the
>>SourceSafe database, so we will see how it goes.
>>
>>Sly
>>
>>
>>
>>>My SourceSafe to Subversion migration script,
>>>http://www.tobiasly.com/svn/, has been updated to prevent extra newlines
>>>from being introduced when migrating comments. I haven't added the
>>>label-recognition logic yet but that should be finished shortly.
>>>
>>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 26 02:47:55 2004