My workflow for testing my changes to our source code on a remote machine is the following:
1) On local machine: Shelve changes that I\'d like to test
2) On remo
Edit: just reread your question - this is a workaround, perhaps not a full solution...
There is a setting in P4Win that allows you to overwrite files when unshelving:
Overwrite workspace files even if they are writeable
I normally use that in combination with another option (again in the gui):
Revert checked our files before unshelving
They solve my problem.
Looking in the console output while running this from the gui, it looks like it is the -f
parameter in the unshelve
command.
p4 unshelve -s <changelist> -f -c <changelist> <files>
I think what you're looking for is p4 revert -w
. From the help:
The -w flag causes files that are open for add to be deleted from the workspace when they are reverted.
Note: I'm using the 2013.2/719516 client against a 2013.2/708877 server, in case that switch was added recently...