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@allafter 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Newbies FAQ] [Linux Kernel Development] [Free Online Dating] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Free Online Dating] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users] [Linux Resources]