perforce

问题 I've been reading about Perforce but haven't found any comprehensive explanation of relationship between workspace and working directory, e.g. how files appear in working directory from workspace, how they are tracked, what inconsistencies are possible between workspace files and working directory files etc. I come from git background, and so I'm looking for the description of workspace and working directory interaction similar to index and working directory interaction in git. 回答1: For

问题 Basically what I want to do is delete a depot off the server. I have access to both P4Admin and the P4Helix. Now I understand that I must first delete all workspaces then streams then delete the depot. But I am looking for a workaround to this process (personally I find it stupid, what if someone left the company and doesn't want to cooperate?), is there one? Can I force delete a depot and its Streams without going to every single possible user that may have used this depot and ask them to

问题 I tried integrating the changes from classic depot to stream depot through p4v. Steps below: 1) I moved to classic deport client which has both depot paths (source & destination paths) in client view. 2) ran p4 merge/integrate from my classic depot. 3) Given target location in p4v in p4merge window. 4) File got opened in my client. 5) Did 'p4 submit'. Giving me this error :- //New_stream/main/temp/sample.txt - warning: cannot submit from non-stream client No files to submit. Submit failed --

问题 I've a branch in P4 at //depot/MyDemoInfo/trunk/Server/My_Service & under My_Service, my entire source code is present. Now, When I'm trying to create a new branch from the above trunk branch, it is giving me error: I'm trying to create a new release branch as shown below: //depot/MyDemoInfo/1.0/Server/My_Service So, I issued below command after adding it in my client specs: p4 integrate //depot/MyDemoInfo/trunk/Server/My_Service/... //depot/MyDemoInfo/1.0/Server/My_Service/... It gives below

问题 p4 changes -l ... shows us the list of check-ins and the description, but it doesn't show the list of files that were modified in the check-in. Is there a way to do that in one command , without the need to create a wrapper script that combines the output of another command like p4 describe or p4 file ? In Subversion, I can do this by running svn log -v . 回答1: The 'files' command can do what you're looking for. An easy way is: p4 files //...@=<changelist> That example will list the files

问题 Steps to repro the issue: Add a file to my P4 server, the file is detected as 'utf8' file type. The file I added is utf8 encoding without BOM. nobomb show in vim p4 client detect it as 'utf8' If I do the same steps on other device, the file type is detected as 'unicode'; Delete the file from local, and then sync it from server. issue occur: the file become utf8 with BOM. sync the file, the file become utf with BOM As you know, BOM in html file can cause lots of issue....Is there anyone who

问题 So, I can import from p4 using git-p4 without any problem. Everything seems to work, but my PNG files (and perhaps others) are getting corrupted. I've read about gitattributes and the line ending issues, but nothing I do seems to change the end result. Broken images. My attributes file is: *.png binary Any ideas? As I understand it, git is supposed to be smart enough to figure out that a png is a binary file without this help. Is this something particular to do with how p4-git pulls the files

问题 I'd like to clone the second half of my repo. It works correctly using the command: git-p4 clone --detect-branches //depot@all So I want to run something like below, but it does not import the files the same way and eventually fails: git-p4 clone --detect-branches //depot@2000,3000 How can I get the second method to work correctly? Update : The output I get right now is that p4 becomes stuck in an infinite loop: current change 32688 trying: earliest latest

问题 I'd like to filter files using RCS keyword expansion so that instances of $Change$ are translated to 1745 rather than the default behaviour of $Change: 1745 $ . I realize that this would prevent future expansions, but that's acceptable for the purposes. Other methods of inserting the changelist number into a file are also welcome. This is the only method I've seen with Perforce that works during submission -- it's just that I'd like to clean it up so that it can be cleanly inserted into

问题 In my primary branch there is a change list with 10 files that I'm trying to integrate into a development branch. All of the outstanding files in the change list should be ignored, and not branched into the target. What are the steps to do the integration so that Perforce does not create the files in the target branch, and ignores the change list files for all future integrations? I originally did an integration with -Dt , and then reverted the 10 files I did not want to be created in the