Perforce obliterate files

Although the file is not removed from disk, you can use -a in conjunction with -b to speed up obliteration of branched files known to exist only as lazy copies. Skip the search of db. The next time a client workspace that refers to these files is synced, any such files in the workspace will also be removed from the workspace.

This is often the desired behavior, for example, in client workspaces on build machines. Obliterating files in revision ranges can also change the behavior of scripts, as revision numbers of files may "skip" obliterated revisions. For instance, the output of p4 filelog after obliterating revisions 2 and 3 might look like this:. In this case, a developer using the 4 in the first line of the output to assume the existence of four change descriptions in the output of p4 filelog would encounter difficulty.

Do not obliterate any files; list the files that would be obliterated with the -y option. In this case, all files in directory dir and below would be subject to deletion with the -y option. Obliterate file from the depot. All history and metadata for every revision of file are erased. Obliterate only the third revision of file. If 3 was the head revision, the new head revision is now 2 and the next revision will be revision 3.

If 3 was not the head revision, the head revision remains unchanged. It does not contain revisions prior to the branch from d. Since p4 snap copied the contents of y. Internal Properties Validation Status. Helix VCS. How To Contact Support Whether you're looking for self-service resources, product downloads, or how to contact Technical Support, we've got lots of options to get the help you need—fast! Request Support. Local Phone Support Looking for help?

Call us to get started. Phone Support. Licensing Questions Do you have a licensing question? Contact Us. Perforce uses cookies to ensure the best experience on our website. By continuing to use this site you consent to our use of cookies. I initially was thinking to obliterate the old revisions from p4admin, since there is the option "obliterate up to revision", but in the case of this folder I'm not sure how this will behave.

There is any way in p4 for keeping only the last 2 revision of all the files in that folder? Or the only doable way is writing a script for checking each file's revision before obliterating it?

Perforce doesn't have an additive relative revision syntax, unfortunately, so you can't use head-2 or anything like that.

Now the label has all the latest revisions that I want to obliterate. I'll double-check with p4 files -a before doing p4 obliterate :. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Best Answer. View this "Best Answer" in the replies below ». Featured in the Community. Which of the following retains the information it's storing when the system power is turned off?

Submit ».