[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: How well does CVS handle other types of data?

From: Paul Sander
Subject: RE: How well does CVS handle other types of data?
Date: Fri, 13 Jul 2001 14:36:08 -0700

>--- Forwarded mail from address@hidden

>Just thought I'd mention one problem with trying to store binary
>files in CVS that nobody has mentioned yet....

>It's not too hard to get diff to run out of memory with binary
>files, (compared to ascii files.)  I have one file in my repository
>that I can't commit to because of this.  Luckily, it's obsolete, and
>the commit that I would like to do is a "cvs remove".  But I can't,
>so it gets checked out all the time and ignored.  Tolerable, but 
>not ideal.  (The file _is_ rather huge to begin with, so maybe it doesn't
>actually come up that much.)

My experience has been that, with RCS, it's not diff that runs out of
memory.  It's RCS.  And RCS has build options that tell it to use temporary
files rather than memory mapped files or other dynamically allocated memory
for the temporary copies.  Setting these allowed me to version binary
files that were multiple gigabytes in size.  (Don't ask why...)

Perhaps the librified RCS that CVS supplies could have this capability

>--- End of forwarded message from address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]