Re: packs and trees

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Jun 20, 2006, 06:13 UTC
Message-ID: <46a038f90606192313l16b16132r1523f5e05ae1566a@mail.gmail.com>
In-Reply-To: <9e4733910606192257y1516e966t848a3b1e29e5667f@mail.gmail.com>

On 6/20/06, Jon Smirl <jonsmirl@gmail.com> wrote:

> The plan is to modify rcs2git from parsecvs to create all of the git
> objects for the tree.

Sounds like a good plan. Have you seen recent discussions about it being impossible to repack usefully when you don't have trees (and resulting performance problems on ext3).

> cvs2svn seems to do a good job at generating the trees.

No doubt. Gut the last stage, and use all the data in the intermediate DBs to run a git import. It's a great plan, and if you can understand that Python code... all yours ;-)

> exactly sure how the changeset detection algorithms in the three apps
> compare, but cvs2svn is not having any trouble building changesets for
> Mozilla. The other two apps have some issues, cvsps throws away some
> of the branches and parsecvs can't complete the analysis.

Have you tried a recent parsecvs from Keith's tree? There's been quite a bit of activity there too. And Keith's interested in sorting out incremental imports too, which you need for a reasonable Moz transition plan as well.

cheers,

martin