From: Kevin Green <Kevin.T.Green@morganstanley.com>
To: git@vger.kernel.org
Subject: Asking again... [Re: how to properly import perforce history?]
Date: Mon, 11 Jun 2007 10:25:25 -0400 [thread overview]
Message-ID: <20070611142525.GN25093@menevado.ms.com> (raw)
In-Reply-To: <20070608202236.GJ25093@menevado.ms.com>
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?
Thanks
--Kevin
On 06/08/07 16:22:36, Kevin Green wrote:
>
> Very new to git. Was hoping this would be much more straightforward and I'm
> assuming I'm just missing something fundamentally easy.
>
> I'm using git-p4import.py which came with my release of git.
>
> I have a small project I'd like to move from perforce to git ( 111 files, 165
> revisions ).
>
> I've used a number of different approaches to do this, all of them resulting
> in my files being deleted.
>
> 1)
> $ git init
> $ git-p4import //depot/path master
>
> bombs out with missing .git/index
>
> 2)
> $ p4 sync ...
> $ git init
> $ git add .
> $ git commit
> $ git-p4import --stitch //depot/path
>
> This imports all the comment history, but deletes all of my files!!
>
> 3)
> $ p4 sync ...
> $ git init
> $ git add .
> $ git commit
> $ git-p4import //depot/path new
> ### new branch with no files, but all my files in master
> $ git checkout master
> $ git merge new
> ### Now I see it deleting all of my files, but it pulls in all of the history.
>
>
> NOTE: All of the commits pulled in have no file information associated with
> them...
>
>
> What am I missing?
>
>
> Thanks
>
> --Kevin
next prev parent reply other threads:[~2007-06-11 14:32 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 ` Kevin Green [this message]
2007-06-11 14:56 ` Asking again... [Re: how to properly import perforce history?] Simon Hausmann
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=20070611142525.GN25093@menevado.ms.com \
--to=kevin.t.green@morganstanley.com \
--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 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).