From: Simon Hausmann <simon@lst.de>
To: git@vger.kernel.org
Subject: Re: Asking again... [Re: how to properly import perforce history?]
Date: Mon, 11 Jun 2007 16:56:33 +0200 [thread overview]
Message-ID: <200706111656.33696.simon@lst.de> (raw)
In-Reply-To: <20070611142525.GN25093@menevado.ms.com>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
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).
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-11 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 20:22 how to properly import perforce history Kevin Green
2007-06-11 14:25 ` Asking again... [Re: how to properly import perforce history?] Kevin Green
2007-06-11 14:56 ` Simon Hausmann [this message]
2007-06-11 15:44 ` Alex Riesen
2007-06-11 18:42 ` Simon Hausmann
2007-06-11 20:12 ` Alex Riesen
2007-06-11 21:20 ` Scott Lamb
2007-06-11 23:16 ` Alex Riesen
2007-06-11 23:41 ` Scott Lamb
2007-06-11 21:46 ` Simon Hausmann
2007-06-12 1:19 ` Han-Wen Nienhuys
2007-06-12 14:12 ` Alex Riesen
2007-06-11 16:41 ` Kevin Green
2007-06-11 20:28 ` Alex Riesen
[not found] ` <20070611194450.GK25093@menevado.ms.com>
[not found] ` <200706112159.34181.simon@lst.de>
2007-06-11 20:51 ` [PATCH] git-p4: check for existence of repo dir before trying to create [Was: Asking again... [Re: how to properly import perforce history?]] Kevin Green
2007-06-11 21:32 ` Simon Hausmann
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=200706111656.33696.simon@lst.de \
--to=simon@lst.de \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.