From: Lars Schneider <email@example.com>
To: Patrick Rouleau <firstname.lastname@example.org>
Subject: Re: git-p4: cloning with a change number does not import all files
Date: Mon, 27 Nov 2017 13:52:17 +0100 [thread overview]
Message-ID: <57A92686-9161-4234-8341-CD6FAD7AE049@gmail.com> (raw)
> On 25 Nov 2017, at 21:35, Patrick Rouleau <email@example.com> wrote:
> I created a git repository with these commands:
> git p4 clone //perforce/path@123456 repo
> cd repo
> git p4 rebase
> Some files created before the change 123456 do not exist in git
> history. I do see why,
> but those files were not modified after that change number.
> If I use "git p4 sync --detect-branches" instead of "git p4 rebase",
> the branch contains
> all the files, but not the main trunk, and they appear to be added in
> the first commit of
> the branch.
> To avoid the problem, I must clone with "@all" or with the change number when
> //perforce/path was created, which is significantly longer.
> P. Rouleau
what is your goal here? Do you want to convert the repo to Git or do you
want to use Git to interact with a P4 repo?
I mainly do the former and use the @all switch. You can greatly reduce
the time if your `git-p4` machine is close to the P4 server and if you
reduce the P4 client spec used for the migration.
next prev parent reply other threads:[~2017-11-27 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 20:35 git-p4: cloning with a change number does not import all files Patrick Rouleau
2017-11-27 12:52 ` Lars Schneider [this message]
2017-11-29 3:48 ` Patrick Rouleau
2017-12-01 12:45 ` Lars Schneider
2017-12-02 15:35 ` Patrick Rouleau
2017-12-02 17:55 ` Luke Diamand
2017-12-02 19:58 ` Patrick Rouleau
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).