New submission from Hedin Meitil <[EMAIL PROTECTED]>: When doing the initial recording of a large repostitory, I get an "Heap exhausted" error.
I can't read Haskell, so I'll have to do some guesswork here. It seems to me that darcs builds up the patch in memory, making sure that dependencies are allright, etc., before writing it to disk. For the initial patch, there shouldn't be any dependencies to take care of, so the patch could just as well be streamed to disk as you go, allowing for much larger repositories to be darcs'ified. For the following patches, the current logic is fine, as they typically won't that big. ---------- messages: 621 nosy: droundy, hejin, tommy priority: wishlist status: unread title: Avoid heap exhaustion when importing large repositories ____________________________________ Darcs issue tracker <[EMAIL PROTECTED]> <http://bugs.darcs.net/issue162> ____________________________________ _______________________________________________ darcs-devel mailing list [email protected] http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
