Reputation: 19333
I deleted a large folder I no longer need from my local workspace, i.e.
//binary_blobs/...
. Now Perforce (command line) is complaining about the
missing files, i.e.:
test.raw - submit change default to delete //binary_blobs/test.raw#1
My goal is to tell the remote server that I've locally deleted the files, and
that the server/depot copy should be left alone. Essentially, I want to update
the "have list" so that it knows I no longer possess this 200GB folder of binary
data. I ran p4 flush //binary_blobs/...
, hoping it would resolve the issue,
but nope: p4 is still locally tracking these files.
So, I decide I'll just tell it to sync this folder at #0
to remove the local
copies of the files via p4 sync -f //binary_blobs/...#0
, but this fails too
due to:
//binary_blobs/test.raw#1 is opened for delete and can't be deleted
Argh! Looks like I have to revert my changes:
p4 revert //binary_blobs/...
Now it's RE-SYNCING all the data over the network again, which will takes days.
Can I tell Perforce, via the command line, to just update the "have list" based on what I locally possess, without re-pulling the entire depot from the remote server?
Upvotes: 0
Views: 212
Reputation: 19333
Finally figured it out. First, I revert while keeping the workspace files as-is:
p4 revert -k //binary_blobs/...
Now I can update to revision #0
:
p4 sync -f //binary_blobs/...#0
Saved me from having to manually re-create my workspace.
Upvotes: 1