From: Patrick Rouleau <prouleau72@gmail.com>
To: git@vger.kernel.org
Subject: git-p4: cloning with a change number does not import all files
Date: Sat, 25 Nov 2017 15:35:56 -0500 [thread overview]
Message-ID: <CAL1_K8AYf1jKDO8+czcqkUxDAuOODgKv9avaiikWi+4zpqenMQ@mail.gmail.com> (raw)
Hi,
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.
Regards,
P. Rouleau
next reply other threads:[~2017-11-25 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 20:35 Patrick Rouleau [this message]
2017-11-27 12:52 ` git-p4: cloning with a change number does not import all files Lars Schneider
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
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
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 \
--in-reply-to=CAL1_K8AYf1jKDO8+czcqkUxDAuOODgKv9avaiikWi+4zpqenMQ@mail.gmail.com \
--to=prouleau72@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).