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, 17:38 UTC
Message-ID
<BANLkTik+Zp1Fvi_zABCtAZH0RKA68n5Svw@mail.gmail.com>
In-Reply-To
<34E33A18-B9C4-4CA9-B96C-79B0E2BDCD44@gmail.com>
Hi Grant,
> The "Branch-foo" that git-p4 is crashing on does have a branchspec in
> Perforce.  I cannot, however guarantee that branchspecs were
> correctly created and used for all integrates in the repository.  It
> was created long before I started working here.

You can create the branch specs now. There is no requirement for them to have been created at the time of the integration.

I've sent a patch to this mailing list [1] that adds the possibility of creating these branches in a gitconfig file. If you feel brave enough, please give it a try. The patch is missing a test case, which I still did not have time to review and send

> Is there a way to limit --detect-branches to only certain branches
> that I can ensure do have branchspecs?

If you have an incremental structure you could limit the cloning to a subset of the directories. I am not aware of any other way. Maybe someone else in the mailing list can shed some light...? :)

Vitor
[1] http://thread.gmane.org/gmane.comp.version-control.git/167998/focus=168000
Previous: Grant LimbergNext: Grant Limberg
Message 6 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.