git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: FusionX86 <fusionx86@gmail.com>
To: git@vger.kernel.org
Subject: git-p4 Question
Date: Mon, 20 Apr 2015 10:41:02 -0600	[thread overview]
Message-ID: <CAFcBi89YqRGqigR1VCJJQtu1D206rP2T8Y-10KvFnvDjXYaN_g@mail.gmail.com> (raw)

Hello,

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. Anyway, I've been playing with git-p4 and
have one question/problem to discuss.

After setting up the p4 cli client I can 'p4 sync' some
//depot/main/app1 which pulls down the files I would expect from the
Perforce server. If I use 'git p4 clone //depot/main/app1', I get:

"Doing initial import of //depot/main/app1/ from revision #head into
refs/remotes/p4/master"

But I don't get any files from that depot/folder pulled down. I can
git p4 clone other depot/folders though and get some files. I suspect
that I'm just not understanding how the git-p4 module works.

Basically, I'm hoping to setup a live sync of Perforce to Git of
certain depots in preparation for the migration. Also, if anyone has
pointers or guides for this type of migration, any help is
appreciated.

             reply	other threads:[~2015-04-20 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 16:41 FusionX86 [this message]
2015-04-20 18:23 ` git-p4 Question Sam Vilain
2015-04-21 13:23   ` FusionX86
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=CAFcBi89YqRGqigR1VCJJQtu1D206rP2T8Y-10KvFnvDjXYaN_g@mail.gmail.com \
    --to=fusionx86@gmail.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).