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

Re: git-p4: commits are visible in history after 'git p4 clone', but not a single file present

From
IDIlya Dogolazky <ilya.dogolazky@nokia.com>
Date
Jun 13, 2012, 12:56 UTC
Message-ID
<4FD88DE0.4050606@nokia.com>
In-Reply-To
<4FD83A08.6070208@nokia.com>
Hi !
06/13/2012 09:58 AM, Ilya Dogolazky написал:
> $ P4CLIENT=xexe1 git p4 submit
> Error: Cannot locate perforce checkout of //xxx/yyy/ in client view

After some playing around with git-p4 script and adding debugging printing I realized, that the solution is to do

$ P4CLIENT=xexe1 git p4 clone //xxx/yyy/zzz@all ~/xexe1 instead of just $ P4CLIENT=xexe1 git p4 clone //xxx/yyy@all ~/xexe1

After that "git-p4 submit" started to work.

I still don't understand p4 enough in order to know why it's happening, but now at least I can clone+change+rebase+submit files into the perforce repository with git-p4, which is great.

Luke, Pete: thanks a lot for your help and patience!
Cheers,
Ilya
Previous: Ilya DogolazkyNext: Luke Diamand
Message 8 of 10 in “git-p4: commits are visible in history after 'git p4 clone', but not a single file present”
  1. Ilya DogolazkyJun 11, 2012
  2. Luke DiamandJun 11, 2012
  3. Ilya DogolazkyJun 11, 2012
  4. Luke DiamandJun 11, 2012
  5. Ilya DogolazkyJun 12, 2012
  6. Pete WyckoffJun 12, 2012
  7. Ilya DogolazkyJun 13, 2012
  8. Ilya DogolazkyJun 13, 2012
  9. Luke DiamandJun 13, 2012
  10. Ilya DogolazkyJun 14, 2012

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.