The “can’t clobber writable file” error happens because Perforce is very cautious about accidentally overwriting (“clobbering”) work that you’ve done in your workspace. The normal Perforce workflow is to p4 sync a file (which puts it into your workspace as read-only) and then to p4 edit it if you want to modify it (this makes … Read more
Shelve the changes in the pending changelist, then run p4 describe -S -du 999
Run p4 opened to see all your opened files and run p4 revert to revert them. Then run p4 changes -c your-client-name -s pending to see all your pending changelists. Since in the first step you reverted all your open files, these changelists will all be empty. Run p4 change -d change-number to delete each … Read more
From the command line: p4 opened -a //depot/Your/Location/… The … indicates that sub folders should be included.
This should list all the shelved changes per user. p4 changes -u <USERNAME> -s shelved
I’m not overly familiar with the blame command, but I assume that you are looking for who changes a particular line of code. The easiest way is to use Perforce’s ‘time lapse view’ available from both p4win and p4v. This tool uses annotate and some other commands to give you a view of the code … Read more
As of version 2012.1, Perforce supports the P4IGNORE environment variable. This allows you to specify files and directories to ignore when using the commands that search for or add new files (p4 add, p4 status, and p4 reconcile). To use an ignore file, create a file in the root of your workspace and give it … Read more
in the P4V application: Open the Workspace dialog: Go to Connection>Edit Current Workspace… change “Workspace root:” to where you like If you have not already moved the files, P4V will offer to copy them for you.
p4 describe -S 1234 should to the trick, see the documentation on describe. To see the file content you would unshelve the files into your workspace (assuming you have a workspace for the same project your colleague is working on). Create a new (empty) changelist with p4 change (results in e.g. 2345), then use p4 … Read more
P4 keeps track of your working copy on the server. This means that Large working copies are processed much faster. I used to have a large SVN project and a simple update took 15 minutes because it had to create a tree of the local working copy (thousands of folders). File access is slow. P4 … Read more