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

Re: [git-p4] Trouble importing all perforce branches into git repository

From
Vitor Antunes <vitor.hda@gmail.com>
Date
May 23, 2011, 10:54 UTC
Message-ID
<BANLkTi=TCyyS7Q=3BnLcG=yhL_boH=w1XA@mail.gmail.com>
In-Reply-To
<398FA881-E4A1-49AC-80F2-2D46E9F2ABB9@gmail.com>
Hi Grant,

I think I saw that happening when there is nothing to import or in situations where the parent of a certain branch does not exist.

Perforce does not strictly require branch definitions to allow a branch structure/flow. It is quite possible that you are integrating stuff around without using "branch specs". When git-p4 is importing your P4 database it will look at all branches available in the server, including ones from other depots. So it is possible that while you are seeing a big list of branches being processed, none apply to the branch structure you are trying to import.

Could you please confirm that you have Perforce branch specs for all branches that you are trying to import?

Thanks, Vitor

Previous: Grant LimbergNext: Grant Limberg
Message 4 of 11 in “[git-p4] Trouble importing all perforce branches into git repository”
  1. Grant LimbergMay 19, 2011
  2. Pete WyckoffMay 22, 2011
  3. Grant LimbergMay 23, 2011
  4. Vitor AntunesMay 23, 2011
  5. Grant LimbergMay 23, 2011
  6. Vitor AntunesMay 23, 2011
  7. Grant LimbergMay 23, 2011
  8. tumikJun 16, 2011
  9. Thomas BergJun 16, 2011
  10. tumikJun 16, 2011
  11. Thomas BergJun 16, 2011

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.