From: Ilya Dogolazky <ilya.dogolazky@nokia.com>
To: git@vger.kernel.org
Subject: git-p4: commits are visible in history after 'git p4 clone', but not a single file present
Date: Mon, 11 Jun 2012 13:03:15 +0300 [thread overview]
Message-ID: <4FD5C263.9010307@nokia.com> (raw)
Hi !
I hope this is the right mailing list for question regarding the usage
of git-p4, sorry if I'm wrong.
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.
Thanks a lot!
-- Ilya Dogolazky
next reply other threads:[~2012-06-11 10:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 10:03 Ilya Dogolazky [this message]
2012-06-11 15:28 ` git-p4: commits are visible in history after 'git p4 clone', but not a single file present Luke Diamand
2012-06-11 19:16 ` Ilya Dogolazky
2012-06-11 22:46 ` Luke Diamand
2012-06-12 9:37 ` Ilya Dogolazky
2012-06-12 22:24 ` Pete Wyckoff
2012-06-13 6:58 ` Ilya Dogolazky
2012-06-13 12:56 ` Ilya Dogolazky
2012-06-13 18:00 ` Luke Diamand
2012-06-14 10:23 ` Ilya Dogolazky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD5C263.9010307@nokia.com \
--to=ilya.dogolazky@nokia.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.