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

From: Kevin Green <kevin.t.green@morganstanley.com>
Date: Jun 11, 2007, 16:41 UTC
Message-ID: <20070611164127.GS25093@menevado.ms.com>
In-Reply-To: <200706111656.33696.simon@lst.de>

On 06/11/07 10:56:33, Simon Hausmann wrote:

Show 23 quoted lines

> On Monday 11 June 2007 16:25:25 Kevin Green wrote:
> > Reading this again, the subject was probably misleading...  Sorry for that.
> >
> > In the meantime I've been scouring the archives looking for the proper way
> > to import p4 history into a project.
> >
> > I'm attempting to use git-p4import.py as that's what came with my version
> > of git.  I ran into the problems below.
> >
> > How can I properly migrate a project from perforce to git?
> 
> *plug* You could try with git-p4 from http://repo.or.cz/w/fast-export.git . It 
> should be just a matter of calling
> 
> 	git-p4 clone //depot/path
> 
> or
> 
> 	git-p4 clone //depot/path@all
> 
> (the former if you just want perforce #head, the latter if you want to import 
> all revisions).
>

Thanks... I'll try this today and post back on my experience. From your usage example here, it seems to behave the way I thought git-p4import.py would.

Is git-p4import.py still used and maintained? 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...

--Kevin