git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-p4: cloning with a change number does not import all files

From
Patrick Rouleau <prouleau72@gmail.com>
Date
Nov 25, 2017, 20:35 UTC
Message-ID
<CAL1_K8AYf1jKDO8+czcqkUxDAuOODgKv9avaiikWi+4zpqenMQ@mail.gmail.com>
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: Lars Schneider
Message 1 of 7 in “git-p4: cloning with a change number does not import all files”
  1. Patrick RouleauNov 25, 2017
  2. Lars SchneiderNov 27, 2017
  3. Patrick RouleauNov 29, 2017
  4. Lars SchneiderDec 1, 2017
  5. Patrick RouleauDec 2, 2017
  6. Luke DiamandDec 2, 2017
  7. Patrick RouleauDec 2, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.