Re: Asking again... [Re: how to properly import perforce history?]

From: Alex Riesen <raa.lkml@gmail.com>
Date: Jun 11, 2007, 20:28 UTC
Message-ID: <20070611202810.GB4649@steel.home>
In-Reply-To: <20070611164127.GS25093@menevado.ms.com>

Kevin Green, Mon, Jun 11, 2007 18:41:27 +0200:

> Is git-p4import.py still used and maintained?

Not really: there is only 5 changes which touch the file and only two of them have something to do with the import.

> I submitted a patch to fix something trivial on Friday, but didn't
> here any response to that either, which led me to believe that it's
> not the tool being used most often for p4->git migration...

That's not the tool. It is the migration from p4 to anything which does not happen too often: this company did very good job tying the customers to this product. Once you reached some critical mass in your perforce repo you cannot simply stop using it and go with something else. Not without much pain, anyway.

Getting the development history out of it is the hardest. I'd say it is impossible, as the states of development directories, unloaded in "clients", are fluid and not recoverable after they are changed. Imagine git with just index and no object database support.