From: Ilya Dogolazky <ilya.dogolazky@nokia.com>
To: Luke Diamand <luke@diamand.org>
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: Tue, 12 Jun 2012 12:37:47 +0300 [thread overview]
Message-ID: <4FD70DEB.7040506@nokia.com> (raw)
In-Reply-To: <4FD67530.1090002@diamand.org>
Hi Luke!
> #!/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 installed p4d on my machine and executed the above script.
It works, the file foo.c is visible in the copy and one line patch is
visible by "git log -p". Everything is fine!
Then I realize, that the "git-p4" call in your script is communicating
with the p4 daemon directly, which is much more simple setup than I
tried to use before. Then I changed the clone command: instead of
$ git p4 clone //kalma/xxx/yyy@all
I now tried
$ git p4 clone //xxx/yyy@all
after setting P4PORT etc to point to the company's perforce server. And
it worked!
Then I even tried
$ git p4 clone //xxx@all
And it worked too (creating a huge git repository with the whole project).
Until today I tried to use the following setup: first clone the whole
perforce repository with p4 command line client to my machine ('kalma'
is its name) and then make a git repository by "git-p4 clone" from this
intermediate location (and it seems I did something wrong there: files
were visible in the intermediate location after the first step, but not
in the end location after git-p4). I read it somewhere in documentation
claiming that it's the only way to use git-p4. But now I see, that it
seems not to be necessary. Please clarify, is it okay to skip this
intermediate location and use git-p4 in the same way as your script does?
And another question, probably connected to above: Now I did this:
$ git p4 clone //xxx/yyy@all
$ cd yyy/zzz
$ edit readme.txt (which was already present there)
$ git commit readme.txt
$ git p4 rebase (Current branch master is up to date)
$ git p4 submit
That last step failed with following messages:
Submitting change 20073
... //xxx/yyy/zzz/readme.txt - warning: cannot submit from non-stream
client
No files to submit.
Submit failed -- fix problems above then use 'p4 submit -c 20073'.
Is it somehow related to my setup?
Cheers,
Ilya
next prev parent reply other threads:[~2012-06-12 9:38 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
2012-06-12 9:37 ` Ilya Dogolazky [this message]
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=4FD70DEB.7040506@nokia.com \
--to=ilya.dogolazky@nokia.com \
--cc=git@vger.kernel.org \
--cc=luke@diamand.org \
--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).