perforce

问题 I'm new to Perforce and, to be honest, I'm hating it. I had about 20 files in my c:\workspaces\perforce directory and I selected all of them and hit the delete key. They were all checked in before I deleted them. I've been pulling my hair out trying to figure out how to get them back (Perforce is sooooo unintuitive) but there's nothing that stands out to a n00b like me to. How can I get the latest revisions back into the directory from Perforce? 回答1: You need to do a force sync. On the

问题 I'm new to Perforce and, to be honest, I'm hating it. I had about 20 files in my c:\workspaces\perforce directory and I selected all of them and hit the delete key. They were all checked in before I deleted them. I've been pulling my hair out trying to figure out how to get them back (Perforce is sooooo unintuitive) but there's nothing that stands out to a n00b like me to. How can I get the latest revisions back into the directory from Perforce? 回答1: You need to do a force sync. On the

问题 I have a perforce client which maps several perforce paths into my local client. These perforce paths are for libraries and the main code line. How do I use git-p4 to setup a clone of the entire client in a separate directory? From what I see git-p4 can only clone specific depot paths. I would like to clone an entire client: suppose my perforce client is test_client. I would like to do: cd git_area cp ../perforce/test_client/.perforce . git-p4 clone or something similar which will pull in all

问题 I am having a problem with git p4 rebase and I don't know how to start diagnosing the issue, much less what the problem is. So I have a git repo cloned from a perforce workspace by git-p4 and it's being used as a remote repo to serve as a bridge so a team can use git against one remote repo and then periodically, I can push the repo's changes back to the workspace. And normally the workflow is either that the person is on the master branch, makes edits, git -a commit s them, git pull s again,

问题 Are there any community MSBuild tasks for Perforce (e.g. even just basic syncing)? Neither the MSBuild Community tasks or MSBuildExtenstion pack seem to have any. 回答1: It looks like the open source MSBuild Contrib project has some p4 tasks. I've never used them before so I can't say how well they work. If they don't work you can always write your own tasks, they are pretty easy if you are able to write .NET code. If you don't want to go that route you can use the Exec task to execute command

问题 I know this has come up before, but there was little in the way of day to day personal experiences in the posts I saw. Only a couple of responses. I'd love to hear from people that use git-p4, or have used git "under the covers" in a Perforce repo, or preferably both. And for those people who just use git underneath another version control, I'd love to hear how you deal with notifying the main version control of changes. Specifically, with git/perforce, when you're done and ready to commit

问题 P4V has been crapping out on me when attempting to resolve a large number of files as part of an integration. I want to be able to do this in the command line. Here's the steps in P4V: Right-click the CL. Choose "Resolve Files..." A dialog will appear. Choose "Merge yours and theirs if no conflicts exist". Click Auto. Can someone translate this into a p4 command line command with correct arguments? 回答1: You can use p4 resolve -am [file ...] which will skip the files with conflicts. If you

问题 Say I created a branch in perforce of our codebase. Here is the branch spec: //depot/code/main/... //depot/code/branch/... Then, in the branch, say I move the branched file a.txt -> b.txt using p4 integrate //depot/code/branch/a.txt //depot/code/branch/b.txt p4 delete //depot/code/branch/a.txt Now, let's say some changes are made to a.txt in main which I would like to have integrated into b.txt in the branch When I try to integrate using the original branch spec, it doesn't reflect the

问题 Is there a way to get Perforce to send you an email on every check to a particular depository? 回答1: Yes. Type "p4 user" to see your user configuration and then under "Reviews:" put the filespec of the area in depot where you'd like to get notified on a check-in, as in: Reviews: //depot/myproject/... See this section of the P4 command reference for more info. 回答2: In p4v (visual client) Connection -> Edit Current User Enter the path to your repository under Reviews This is correct for OSX &

问题 Every time I rename a file in Perforce it actually deletes an old file and adds a new one. As a result the new file doesn't share the old's file history. Is there an easy way doing it? 回答1: Are you using P4V? It doesn't really delete and add it, it will branch it and then delete the old file (you will see that the new file shows up with the #branch action). That way, the new file will retain the history. It's sometimes not immediately visible, but if you choose to "show branching history",