Re: From P4 to Git

From: Alex Riesen <raa.lkml@gmail.com>
Date: Aug 3, 2009, 21:51 UTC
Message-ID: <20090803215137.GC3759@blimp.localdomain>
In-Reply-To: <1249331540.12801.10.camel@maia.lan>

Sam Vilain, Mon, Aug 03, 2009 22:32:20 +0200:

Show 8 quoted lines

> On Mon, 2009-08-03 at 15:50 +0200, Alex Riesen wrote:
> > "varios options"? Operations? As when working on a live server?
> > Aren't P4 changelist numbers always increasing? Or you mean
> > the protection against multiple running instances of p4raw,
> > so it is also parallelizable?
> 
> The "live" parts are never touched - only the write-only files that
> perforce writes; and the rcs files are read using rcs.

I always felt Perforce had a touch of pure evil...

> All you need is the RCS backing files, a 'checkpoint' and (optionally)
> 'journal' files.  No access to the live perforce DBs is required.

Which in my case is all the same. I don't dare to ask, frankly.

Show 10 quoted lines

> > That's were I hoped your project could help. I thought, if I pull in all the
> > needed changelists (selected by path/CL), there may be a way to
> > recreate a mergeable history out of this dump. At least, one involving less
> > labor then I have to do now.
> 
> Yeah... well the design of my tool is that it needs to have the perforce
> internal information.  But really you can probably consider the
> converter orphaned, I have no current need to work on it; it served a
> purpose, which was converting perl's perforce to perl.git, and that's
> history now.

Thanks anyway for bringing it to public attention. At least, it is known to be done once. Could be an encouragement for next one to try. A guide, even.