| Perforce 2000.2 Command Reference (2000.2.cr.1) | ||
|
<< Previous Chapter p4 lock |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 opened |
Use p4 obliterate with caution. This is the only command in Perforce that actually removes file data.
p4 obliterate requires at least one file pattern as an argument. To actually perform the obliteration, the -y flag is required; without it, p4 obliterate merely tells you what it would do without actually performing the obliteration.
The -z flag is used with branches; after branching a file from one area of the depot into another. When a branch is made, a "lazy copy" is performed - the file itself isn't copied; only a record of the branch is made. If you want to "obliterate" the lazy copy performed by the branch, thereby creating an extra copy of the file in the depot, use p4 obliterate -z on it. Note that this typically increases disk space usage.
|
-y filespec |
Perform the obliterate operation. Without this flag, p4 obliterate merely reports what it would do. |
|
-z filespec |
Undo "lazy copies" only; remove no files nor metadata. This option is most commonly used when working with branches in order to ensure that no other files in the database refer to the named files. |
|
See the Global Options section. |
| Perforce 2000.2 Command Reference (2000.2.cr.1) | ||
|
<< Previous Chapter p4 lock |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 opened |