Converting CVS repository with huge binary files

[Greg Ward]

On Wed, Jun 10, 2009 at 11:03 AM, Stephen Rasku<srasku at gmail.com> wrote:
> I just tried to convert a CVS module to Mercurial.  It has huge binary
> files and it failed after 6 hours after converting only 10 of over 60
> changesets.  I was using the --datesort option.  Would it help to omit
> it?  Is there anything else I can do?  It looks like the CVS server
> has 4G of RAM.

My deepest sympathies.  I think you'll find that Mercurial is not
designed to track large binary files.  (Around here, SCM stands for
"source code management".)  Think of the space overhead of all that
history in *every* *single* *clone*.  Then consider that space
overhead = time overhead when cloning.

You should probably take a look at the bigfiles extensions.  As for
converting your CVS history, I suspect you are on your own.  Good
luck!

Greg