git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luke Diamand <luke@diamand.org>
To: Ilya Dogolazky <ilya.dogolazky@nokia.com>
Cc: git@vger.kernel.org, Pete Wyckoff <pw@padd.com>
Subject: Re: git-p4: commits are visible in history after 'git p4 clone', but not a single file present
Date: Mon, 11 Jun 2012 23:46:08 +0100	[thread overview]
Message-ID: <4FD67530.1090002@diamand.org> (raw)
In-Reply-To: <4FD6440C.7090900@nokia.com>

On 11/06/12 20:16, Ilya Dogolazky wrote:
> Hi Luke!
> 
> 06/11/2012 06:28 PM, ext Luke Diamand написал:
>> If you do something like "p4 describe 17473" what does that show?
> First I see a line containing the change number, my colleague's name and 
> date, then the commit title (identical to one printed by "git log"), 
> then a list of files [every line begins with "... //xxx/yyy/"], then the 
> word "Differences" and then something looking very much like output of 
> 'diff' command (the actual commit differences).
> 
>> Are the files changed all contained with //kalma/xxx/yyy?
> Yes, they are.
> 
>> It could be that there's a p4 version problem going on - which version
>> of p4 are you
>> using?
> The output of 'p4 -V' contains "Rev. P4/LINUX26X86/2012.1/459601 
> (2012/05/11)". That's probably the version of my command line client.
> 
> The output of "p4 info" contains "P4D/LINUX26X86_64/2011.1/428451 
> (2012/03/08)" --- that's probably the version of the server.
> 
> The version of git installation (by debian package) is 1:1.7.10-1 (as 
> reported by "dpkg -l git"). The package contains the file 
> "/usr/share/doc/git/contrib/fast-import/git-p4" which I copied to 
> $HOME/bin/git-p4 in order to have in $PATH and with executable bit. 
> Could it be, that I did something wrong here by making this manually?

That version of git-p4 seems different to the one in the repo. I think it's just a bit older.

> 
>  > And which platform are you using?
> Debian GNU/Linux.
> 
> I hope I provided all the needed information, of not please ask for more.

Can you try an experiment please. Try running the following commands. When I run them I get out a file that looks correct.

#!/bin/sh
export P4PORT=localhost:1234
mkdir db cli
(cd db && p4d &)
sleep 2
(cd cli && EDITOR=: p4 client && date >foo.c && p4 add foo.c && p4 submit -d 'x')
git-p4 clone //depot@all

I've been trying out Debian's 1.7.10.1 and it seems fine, other than having a slightly old version of git-p4 and it not being installed properly.


> 
> Cheers,
> 
> Ilya

  reply	other threads:[~2012-06-11 22:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 10:03 git-p4: commits are visible in history after 'git p4 clone', but not a single file present Ilya Dogolazky
2012-06-11 15:28 ` Luke Diamand
2012-06-11 19:16   ` Ilya Dogolazky
2012-06-11 22:46     ` Luke Diamand [this message]
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=4FD67530.1090002@diamand.org \
    --to=luke@diamand.org \
    --cc=git@vger.kernel.org \
    --cc=ilya.dogolazky@nokia.com \
    --cc=pw@padd.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).