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
Ttumik <tumik@tuomisalo.com>
Date
Jun 16, 2011, 08:28 UTC
Message-ID
<1308212906486-6482174.post@n2.nabble.com>
In-Reply-To
<0AC6DD14-3042-4A18-91AC-1CE77D8B4CD2@gmail.com>
Grant Limberg wrote:
Show 6 quoted lines
> 
> I think I just figured out the problem.  The branch mapping between
> //project/MAIN/... and //project/Branch-foo/... was done backwards, thus
> git-p4 was expecting Branch-foo to be a parent of MAIN when the inverse
> was actually true.
>

Did you get it working so that the branch integrates at Perforce show up as merges in git? I have been trying to do this for tens of hours now and just can't get it working.. I have tried making the branch mapping both ways, and even both at the same time but with no success.

I have succesfully imported the two testing branches to git, but if I look at it in gitk for example, the history is linear and there are no merges from the other branch (it shows up as a normal commit, without the parent from other branch, just adding all lines that the merging did). in p4v it shows up as it should!

-- View this message in context: http://git.661346.n2.nabble.com/git-p4-Trouble-importing-all-perforce-branches-into-git-repository-tp6383422p6482174.html Sent from the git mailing list archive at Nabble.com.

Previous: Grant LimbergNext: Thomas Berg
Message 8 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.