The Darcs Revision Control System
Posted Nov 11, 2004 13:56 UTC (Thu) by zooko
In reply to: The Darcs Revision Control System
Parent article: The Darcs Revision Control System
Oh, and another known issue in darcs v1.0 is that the initial "get" (equivalent to a cvs "checkout") stores the entire history in RAM at one point. For example, I'm now doing a "darcs get" on the Linux kernel, and it is using 504 MB virtual...
After I've finished this darcs get, I'll subsequently be able to do "darcs pulls" to update the kernel source while using only an amount of RAM proportional to the new patches that I'm getting.
to post comments)