git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Sam Vilain <sam@vilain.net>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Arnaud Bailly <abailly@oqube.com>,
	git@vger.kernel.org
Subject: Re: From P4 to Git
Date: Mon, 3 Aug 2009 23:51:37 +0200	[thread overview]
Message-ID: <20090803215137.GC3759@blimp.localdomain> (raw)
In-Reply-To: <1249331540.12801.10.camel@maia.lan>

Sam Vilain, Mon, Aug 03, 2009 22:32:20 +0200:
> 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.

> > 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.

  reply	other threads:[~2009-08-03 21:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 20:14 From P4 to Git Arnaud Bailly
2009-07-28 20:32 ` david
2009-07-28 21:10 ` Jakub Narebski
     [not found]   ` <85r5vxbd8e.fsf@oqube.com>
2009-07-31  9:22     ` Jakub Narebski
2009-07-31 11:14       ` Alex Riesen
2009-08-03  7:49         ` Sam Vilain
2009-08-03  8:47           ` Alex Riesen
2009-08-03 11:30             ` Sam Vilain
2009-08-03 13:50               ` Alex Riesen
2009-08-03 20:32                 ` Sam Vilain
2009-08-03 21:51                   ` Alex Riesen [this message]
2009-08-04  0:29                     ` Sam Vilain
2009-08-02  7:16       ` Sam Vilain
2009-08-04 12:31       ` Arnaud Bailly
2009-08-04 12:35         ` Peter Baumann
2009-08-03 21:37   ` John Tapsell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090803215137.GC3759@blimp.localdomain \
    --to=raa.lkml@gmail.com \
    --cc=abailly@oqube.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=sam@vilain.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).