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

bug in git-p4?

From
MCMercier, Carl <cmercier@websense.com>
Date
May 4, 2009, 19:20 UTC
Message-ID
<F98DA2FE6F6C464C860149518BD861CC3B3C13440A@SSDEXCH2.websense.com>
Hello all,
I've been trying to use git-p4 without much success.  My setup is very simple:
- 1 existing Git repo (with data)
- 1 existing P4 depot (with an empty subdirectory)
- We commit and push to Git and our company requires all the code to be stored in P4 (in the p4 empty subdir).
Here's what I did:

cd /root/p4-repo/SecTech git clone /home/git/repositories/web website cd website git-p4 sync //SecTech/website git branch --track p4-master p4/master git checkout p4-master git merge master git-p4 submit

CRASHES WITH: Perforce checkout for depot path //SecTech/website/ located at /root/p4-repo/SecTech/website/ Syncronizing p4 checkout... ... - file(s) up-to-date. Applying 32a1b2fe93f48c044d04ca37a276fe66afc988ce initial import

fatal: ambiguous argument '32a1b2fe93f48c044d04ca37a276fe66afc988ce^': unknown revision or path not in the working tree. Use '--' to separate paths from revisions Command failed: git diff-tree -r "32a1b2fe93f48c044d04ca37a276fe66afc988ce^" "32a1b2fe93f48c044d04ca37a276fe66afc988ce"

Am I doing something wrong or is there a bug in git-p4?
I'm a bit confused right now.  Thanks!
Carl
 Protected by Websense Hosted Email Security -- www.websense.com 
Next: Tor Arvid Lund
Message 1 of 4 in “bug in git-p4?”
  1. Mercier, CarlMay 4, 2009
  2. Tor Arvid LundMay 8, 2009
  3. Carl MercierMay 8, 2009
  4. Daniel BarkalowMay 8, 2009

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.