On 5/23/06, Donnie Berkholz <spyderous@xxxxxxxxxx> wrote:
So it seems the problem is in cvs itself. I will try another run with -L now.
What version of cvs are you using? Perhaps trying a different one? The dev machine where I am running the import is a slug! It's still working on it, only gotten to 7700 commits, with the cvsimport process stable at 28MB RAM and cvs stable at 4MB. cheers, martin - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html