Re: Perl 5 now uses Git for version control

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Dec 22, 2008, 23:24 UTC
Message-ID: <alpine.LNX.1.00.0812221608410.19665@iabervon.org>
In-Reply-To: <9b18b3110812220332u4cae3a89rf957cbf96af530bf@mail.gmail.com>

On Mon, 22 Dec 2008, demerphq wrote:

Show 9 quoted lines

> In true open source style, Sam Vilain converted Perl's history from
> Perforce to Git. He did the work both in his spare time and in time
> donated by his employer, Catalyst IT. He spent more than a year building
> custom tools to transform 21 years of Perl history into the first
> ever unified repository of every single change to Perl. In addition
> to changes from Perforce, Sam patched together a comprehensive view
> of Perl's history incorporating publicly available snapshot releases,
> changes from historical mailing list archives and patch sets recovered
> from the hard drives of previous Perl release engineers.

At some point, some of the custom tools were visible to the public (although not widely announced), and they include such things as an elaborate algorithm to figure out what a perforce depot's contents is supposed to mean in a number of weird cases. Are these going to be officially released, or are they considered to have served their purpose and be no longer interesting?

I'd be interested to see the final version, and I think it would be useful to anyone working on interoperation between perforce and git (even though the actual code needs a copy of the perforce database and is not incremental).

	-Daniel
*This .sig left intentionally blank*