p4 revert
Synopsis
Discard changes made to open files.
Syntax
p4 [g-opts
] revert [-a -n -k -w]
[-c change
]
[-C client
]
file
…
Description
Use p4 revert to discard changes made to open files,
reverting them to the revisions last synced from the depot (with
p4 sync). This command
also removes the reverted files from the pending changelists with which
they're associated. An administrator can use the -C
option to revert another user's open files.
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. When you revert files you've opened with
p4 move, only the file
open for move/add
can be reverted.
Options
|
Revert only those files that haven't changed (in terms of content or filetype) since they were opened. The only files reverted are those whose client revisions are:
|
|
Reverts only those files in the specified changelist. |
|
Revert another user's open files. This option implies the
This option is also useful in freeing up exclusive locks held on an edge server; in this case, the command needs to be directed where the client resides. For example: p4 revert -C SusanClient //depot/src/x.cc |
|
Keep workspace files; the file(s) are removed from any changelists and Perforce records that the files as being no longer open, but the file(s) are unchanged in the client workspace. |
|
List the files that would be reverted without actually performing the revert. This lets you make sure the revert does what you think it does before actually reverting the files. |
|
Files that are open for |
|
See “Global Options”. |
Usage Notes
Can File Arguments Use Revision Specifier? |
Can File Arguments Use Revision Range? |
Minimal Access Level Required |
---|---|---|
No |
No |
|
-
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
option. -
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
p4 revert //... |
Revert every file you have open, in every one of your pending changelists, to its pre-opened state. |
p4 revert -c default //... |
Revert every file open in the default changelist to its pre-opened state. |
p4 revert -n *.txt |
Preview a reversion of all open |
p4 revert -c 31 *.txt |
Revert all |
p4 revert -a |
Revert all unchanged files. This command is often used before submitting a changelist. |