From: Luke Diamand <luke@diamand.org>
To: Sandeep <varshneysan@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: git-p4 is not cloning perforce code properly
Date: Tue, 10 Feb 2015 15:27:59 +0000 [thread overview]
Message-ID: <CAE5ih78VwwSFcXxXopbmKFoi_HP_9RU_KQFr_h5GRyfeq8b73w@mail.gmail.com> (raw)
In-Reply-To: <1423576488362-7625215.post@n2.nabble.com>
When you say "skipping", can you be more specific please? What command
line are you using?
If I want to clone the P4 tree at the current revision, I do something like:
$ git p4 clone //depot/sometree/...
That gets me just a single revision.
If I want all revisions back to the start of time, I do:
$ git p4 clone //depot/sometree/...@all
Thanks,
Luke
On 10 February 2015 at 13:54, Sandeep <varshneysan@gmail.com> wrote:
> Dear All,
>
> I am trying to clone perforce branch from git to my local drive, but it's
> skipping too many files and change list while fetching it from perforce.
>
> it'll be very helpful if anyone can suggest me about how to git rid with
> this issue.
>
> Thanks in Advance,
> Sandeep
>
>
>
> --
> View this message in context: http://git.661346.n2.nabble.com/git-p4-is-not-cloning-perforce-code-properly-tp7625215.html
> Sent from the git mailing list archive at Nabble.com.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-02-10 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 13:54 git-p4 is not cloning perforce code properly Sandeep
2015-02-10 15:27 ` Luke Diamand [this message]
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=CAE5ih78VwwSFcXxXopbmKFoi_HP_9RU_KQFr_h5GRyfeq8b73w@mail.gmail.com \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=varshneysan@gmail.com \
/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).