Hi Miklos, > > I have no idea what is the size of your repo. About a year ago I had to > convert a repo with about 30k patches. I had to do it fast, so I did not > do proper solutions, but hacks. It's available here: > > http://vmiklos.hu/project/tailor/
I tried this a few months ago. I cannot remember *why* it didn't work for me unfortunately. Have there been any updates to it in the last 2-3 months? If so, I'll try it again. > During the last year I submitted back most of the changes to tailor, but > the performance issue is still there. I broke the possibility of an > incremental conversion, but this way I was able to convert such a big > repo, too. > > NOTE: IIRC there were a few differences when I replaced _darcs with > .git, but they were really minor, so I would not worry about it. > > If you use fast-import... > > http://repo.or.cz/w/darcs2git.git > > did you try this one? > > It properly parses the darcs patch format and maps darcs conflict > resolutions to git merges. My problem with it was it did not handle > special authors names, like empty author and other small problems. > > I also did a lot of work on tailor when I found darcs2git. But I think > if you want to work on something, darcs2git would worth at least a look. And I've also tried this one. The problem I have found is that any darcs conversion tool that relies on invoking darcs itself to do the conversion always hits the exponential time/space bug and fails after a few hours when all of my memory (4GB) and all of my swap (8GB) is exhausted. > > Ah and sorry for not commenting your code, but I don't know Ruby at all. > ;-) No worries :) Thanks for the suggestions. -- James. -- Woody Allen - "I am not afraid of death, I just don't want to be there when it happens." _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
