Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 counters |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 depot |
Although it will appear that a deleted file has been deleted from the depot, the file is never truly deleted, as older revisions of the same file are always accessible. Instead, a new head revision of the file is created which marks the file as being deleted. If p4 sync is used to bring the head revision of this file into another workspace, the file is deleted from that workspace.
A file that is open for deletion will not appear on the client's have list.
-c change# |
Opens the files for delete within the specified changelist. If this flag is not provided, the files are linked to the default changelist. |
-n |
Preview which files would be opened for delete, without actually changing any files or metadata. |
See the Global Options section. |
p4 delete //depot/README |
Opens the file called README in the depot's top level directory for deletion. The corresponding file within the client workspace is immediately deleted, but the file is not deleted from the depot until the default changelist is submitted. |
p4 delete -c 40 file |
Opens file in the current client workspace for deletion. The file is immediately removed from the client workspace, but won't be deleted from the depot until changelist 40 is sent to the server with p4 submit. |
Perforce 2006.1 Command Reference | ||
<< Previous Chapter p4 counters |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 depot |