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

git-p4: submit to blank p4 repository help please

From
RPReynolds, Stephen (GE EntSol, Intelligent Platforms) <stephen.reynolds@gefanuc.com>
Date
Jun 4, 2009, 07:16 UTC
Message-ID
<F61C2CF29BF32C4A805C6C029452B92004756039@LONMLVEM06.e2k.ad.ge.com>
Hi

There was some discussion of this under the topic "bug in git-p4?" but I could see no resolution so I am putting the question out again.

Git-p4 does not seem to work (for me at least) when you try to submit a git repository to a blank p4 repository. It seems that you have to have pulled your git repository from p4 originally in order for it to work?

This is the kind of thing I have typically been trying  
git-p4 clone //depot/firmware/fred/bloggs.git

(//depot/firmware/fred/bloggs.git is a folder synced to an empty p4 repository)

cd bloggs
(there is now an empty git repository here)

If I then pull from a git repository into the newly created bloggs.git and do git-p4 submit

I get...

Syncronizing p4 checkout... ... - file(s) up-to-date. Applying 0b666f81da14bf46cada222856762f7fd6641c26 Initial revision

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

I have tried to checkout pre-existing files from P4, change them in git and put them back and that works fine.

I am using the git 1.6.3.1.fc9 rpms with the git-p4 taken from the git-1.6.3.1 source tree.

Thanks for your help
Steve
Message 1 of 1 in “git-p4: submit to blank p4 repository help please”
  1. Reynolds, Stephen (GE EntSol, Intelligent Platforms)Jun 4, 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.