From: FusionX86 <fusionx86@gmail.com>
To: Sam Vilain <sam@vilain.net>
Cc: git@vger.kernel.org
Subject: Re: git-p4 Question
Date: Tue, 21 Apr 2015 07:23:51 -0600 [thread overview]
Message-ID: <CAFcBi88CwmJ=bxf92BWKLB2m25jnJFD6jpFPYog9Hdneen38DQ@mail.gmail.com> (raw)
In-Reply-To: <5535443C.1060600@vilain.net>
Thanks Sam, I'll check it out.
On Mon, Apr 20, 2015 at 12:23 PM, Sam Vilain <sam@vilain.net> wrote:
> On 04/20/2015 09:41 AM, FusionX86 wrote:
>>
>> Hopefully this is an appropriate place to ask questions about git-p4.
>>
>> I started at a company that wants to migrate from Perforce to Git. I'm
>> new to Perforce and have been trying to learn just enough about it to
>> get through this migration.
>
>
> You might also like to check out my git-p4raw project which imports directly
> from the raw repository files into a git repo using git fast-import
>
> http://github.com/samv/git-p4raw
>
> Apparently it's my most popular github project :-). YMMV.
>
> Sam.
next prev parent reply other threads:[~2015-04-21 13:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 16:41 git-p4 Question FusionX86
2015-04-20 18:23 ` Sam Vilain
2015-04-21 13:23 ` FusionX86 [this message]
2015-04-20 19:26 ` Luke Diamand
2015-04-21 13:33 ` FusionX86
2015-04-21 16:53 ` Luke Diamand
2015-04-23 13:42 ` FusionX86
2015-04-24 9:20 ` Luke Diamand
2015-04-24 14:36 ` FusionX86
2015-04-26 22:27 ` Luke Diamand
-- strict thread matches above, loose matches on Subject: below --
2015-04-20 16:29 Fusion Xavier
2007-08-10 2:53 git-p4 question Govind Salinas
2007-08-10 8:06 ` Alex Riesen
2007-08-10 8:10 ` Alex Riesen
2007-08-10 15:17 ` Govind Salinas
2007-08-10 16:25 ` Alex Riesen
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='CAFcBi88CwmJ=bxf92BWKLB2m25jnJFD6jpFPYog9Hdneen38DQ@mail.gmail.com' \
--to=fusionx86@gmail.com \
--cc=git@vger.kernel.org \
--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).