perforce

I have a file I need to move that's already under perforce. Once moved it needs some editing - update the package, etc - appropriate to its new location. Should I submit the move changespec and then reopen it for edit, or can I do this in one go? If so, what is the appropriate sequence of events? I have done this before in one go, but depending on your build process, I recommend against it. What I generally do is this: Move the file. If the move needs a change in order to compile, open it for edit and make those changes. Submit the changes, telling perforce to reopen the files for editing.

We are using perforce as a source control for Visual studio solution. Working with P4 and P4V. Is it possible to add client side pre-commit hook? for instance to ensure the word "debugger;" is not exist in *.js files. Could find something in Google. Thanks. Perforce triggers can be used to enforce such a policy, but they run in the server, not client-side. So most sites that I'm aware of would enforce a rule such as the one you describe using a change-content trigger in the server. http://www.perforce.com/perforce/doc.current/manuals/cmdref/triggers.html It's not obvious from your question why

xcode4 doesn't support Perforce? I add a repository in xcode4. Only subversion and Git to choose. how to add a perforce repository? thank you. I threw together a couple of Automator services that let you bind hotkeys for p4 edit/p4 add on the currently open file in Xcode 4. It's not ideal, but it beats switching to terminal or p4v. https://github.com/jcohen/xcode4-perforce-services It's also useful to note that there is a setting in Preferences/Behaviors to add behaviors to particular actions. One of those is Unlock File, which can be bound to a shell script, like the one here: #!/bin/sh

After deleting my Svn repo by accident the other day I wanted to try something else and I have chosen Perforce as my current versioning tool testing ground. It is going great and I am liking what am seeing in Perforce. Here is my problem. I have submitted my files to my Perforce server and then used my client pcs to grab those projects from the master Perforce server. Now all works great except that I realized that it is possible to use more than a single "depot" in Perforce, and it makes sense to me that I should just move some of those projects to another depot fpr the sake of organization

I'm using Perforce with Vim on Windows. I currently have an auto command set up to open a read-only file for edit when changing it: au FileChangedRO * !p4 edit <afile> Is there any way to set up a similar auto command to execute p4 edit when attempting to write a read-only file rather than edit it? You can use an auto command attached to the BufWritePre event, that checks whether the file is read only or not and executes p4 edit on demand. Something like: autocmd BufWritePre * :if &readonly | !p4 edit % You can give the perforce plugin a shot. I find it very useful. 来源： https://stackoverflow

I want a fast solution that does not require force sync that will put a specified directory to its original repository state. same files may be removed from disk same files may be added from disk some files may be modified on disk some files may be marked for removal, addition or modification in perforce All I want is to be sure that after if run the command I will have none of these. p4 -f sync is not an option, I need a faster solution that does minimize networks usage. Just in case someone asks, perforce proxy is out of discussion. I do know that a partial solution is: p4 diff -sd -se /

I'd like to know how to convert Perforce depot locations to client view locations for the purpose of script writing. I have a script that first checks out a file for edit in perforce and then interacts with the file. I need to have the depot location (i.e. \Projects\Project6) converted to the client view location. (i.e. d:\Projects\Project6). Is this possible? I have always used the p4 where command for this. Here is its description from the built-in help: where -- Show how file names map through the client view p4 where [ file ... ] Where shows how the named files map through the client view.