Previous Table of Contents Index Next
Perforce 2012.1: Command Reference



p4 revert
Synopsis
Discard changes made to open files.
Syntax
p4 [g-opts] revert [ -a -n -k -c changelist# ] file...
Description
Use p4 revert to discard changes made to open files, reverting them to the revisions last p4 synced from the depot. This command also removes the reverted files from the pending changelists with which they're associated.
When you revert files you opened with p4 delete, the files are reinstated in the client workspace. When you revert files that have been opened by p4 add, Perforce leaves the client workspace files intact. When you revert files you've opened with p4 integrate, Perforce removes the files from the client workspace.
Options
open for integrate via p4 integrate and have not yet been resolved with p4 resolve.
Keep workspace files; the file(s) are removed from any changelists, and the server records the files as being no longer open, but the file(s) are unchanged in the client workspace.
-c changelist#
Usage Notes
Can File Arguments Use
Revision Specifier?
p4 revert differs from most Perforce commands in that it usually requires a file argument. The files that are reverted are those that lie in the intersection of the command line file arguments and the client view.
You don't need to specify a file argument when using the -a flag.
Reverting a file that has been opened for edit will overwrite any changes you have made to the file since the file was opened. It may be prudent to use p4 revert -n to preview the results before running p4 revert.
Examples
Revert every file you have open, in every one of your pending changelists, to its pre-opened state.
Preview a reversion of all open .txt files in the current directory, but don't actually perform the revert.
Revert all .txt files in the current directory that were open in changelist 31.
Revert all unchanged files. This command is often used before submitting a changelist.
Related Commands
To forcibly bring the client workspace in sync with the files that Perforce thinks you have, overwriting any unopened, writable files in the process.


Previous Table of Contents Index Next

Perforce 2012.1: Command Reference
Copyright 1999-2012 Perforce Software.