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
Grant Limberg <glimberg@gmail.com>
Date
May 23, 2011, 03:27 UTC
Message-ID
<398FA881-E4A1-49AC-80F2-2D46E9F2ABB9@gmail.com>
In-Reply-To
<20110522114917.GA19927@arf.padd.com>
On May 22, 2011, at 4:49 AM, Pete Wyckoff wrote:
Show 19 quoted lines
> glimberg@gmail.com wrote on Thu, 19 May 2011 19:32 +0000:
>> [git-p4 automatic branch detection]
>>> git p4 clone --verbose --detect-branches --max-changes=100 //project/...@all
> 
> I worry that --max-changes prevents it from pulling in the
> ref for Branch-foo, and this confuses the automatic branch
> detection that assumes it has all its parents.
> 
> It would certainly be more reliable if you did "git-p4 sync
> --branch foo //project/foo@all" for each branch you care about.
> 
> Vitor has some modifications to auto-branch detection that might
> be useful, or maybe some thoughts as to what's going on.
> 
> 		-- Pete
> 
> (Vitor: full mail is here:
> http://article.gmane.org/gmane.comp.version-control.git/173996/ )
> 
Removing --max-changes=100 has no effect on the crash I'm experiencing.   Same crash still happens on the very first imported commit.
If i do "git-p4 sync --branch foo //project/foo@all" for each branch, does that convert 'p4 integrate' commands into git merges?  I"m trying to keep all history intact when importing from p4 into git.
Thanks,
-Grant
Previous: Pete WyckoffNext: Vitor Antunes
Message 3 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.