Re: Importing Mozilla CVS into git

From: Keith Packard <keithp@keithp.com>
Date: Jun 7, 2006, 00:12 UTC
Message-ID: <1149639142.28173.37.camel@neko.keithp.com>
In-Reply-To: <46a038f90606061257v569aefackc4920a20f2970b0f@mail.gmail.com>

On Wed, 2006-06-07 at 07:57 +1200, Martin Langhoff wrote:

> git-cvsimport has a memory leak that I've been chasing for a while and
> I'll eventually fix, so it should fit in 32MB comfortably. cvsps is
> memory bound, and will probably take quite a bit of work to fix that.
> However, I suspect we can make it a lot more efficient.

Yeah, parsecvs is a memory pig as well -- it builds a giant in-memory representation of the entire project history using flat lists of files for every revision, just like git used to do. Fixing that should make it run in small amounts of memory; it only needs 40 bytes per file revision for the raw data as it converts the cvs files to git objects as it reads them, saving only the hash value in memory.

Not relying on cvsps has been a huge feature though; cvsps loses a tremendous amount of data, along with making several gross and difficult to fix errors in project history from several of my repositories.

-- 
keith.packard@intel.com