Re: git-p4: commits are visible in history after 'git p4 clone', but not a single file present
From: Luke Diamand <hidden>
Date: 2016-06-15 22:54:02
On Mon, Jun 11, 2012 at 11:03 AM, Ilya Dogolazky [off-list ref] wrote:
Hi ! I hope this is the right mailing list for question regarding the usage of git-p4, sorry if I'm wrong.
This is the right place!
Here is my problem: I'm issuing the command 'git p4 clone //kalma/xxx/yyy@all'. (the depot //kalma/xxx/yyy/ exists on my machine and is full of files). After this command the directory 'yyy' is created and the history of commits is visible there by 'git log -p'. Every commit contains author name, a title (related to the project I'm working on, so obviously coming from perforce depot) and a single line looking like this: [git-p4: depot-paths = "//kalma/xxx/yyy/": change = 17473] Beside of that, the commit is empty: not a single line of code is changed/added. And the directory 'yyy' contains only the '.git' subdirectory, so not a single file of the project is visible. Please help me to understand what could be going on there, and what could I have done wrong.
If you do something like "p4 describe 17473" what does that show? Are the files changed all contained with //kalma/xxx/yyy? It could be that there's a p4 version problem going on - which version of p4 are you using? And which platform are you using? Thanks, Luke