p4 move
Synopsis
Move (rename) a file from one location to another.
Syntax
p4 [g-opts
] move
[-c change
] [-f -n -k]
[-t filetype
]
fromFile
toFile
Description
The p4 move command takes a file already opened for edit or add and moves it to the destination provided.
An open file can be moved many times before it is submitted; moving a file back to its original location undoes the pending move, leaving it open for edit. Using p4 revert on a moved file both undoes the move and reverts the unsubmitted content.
Options
|
If a changelist number is provided, the files are opened in the numbered pending changelist. |
|
If a filetype is specified, the file is reopened as the new filetype. |
|
Force a move to an existing target file. The file must be synced, but not opened. The originating source file will no longer be synced to the workspace. If you use p4 move -f, you will need to resolve the move before submitting the changelist. |
|
Keep existing workspace files by bypassing the renaming in the client workspace. Use p4 move -k only in the context of reconciling work performed while disconnected from the Perforce service. |
|
Preview the move that would be performed, without actually moving files. |
|
See “Global Options”. |
Usage Notes
Can File Arguments Use Revision Specifier? |
Can File Arguments Use Revision Range? |
Minimal Access Level Required |
---|---|---|
|
No |
|
-
Files must be open for
add
or open foredit
before they can be moved. -
To move and resolve a file that is open for edit but has been renamed at the head revision, you can use the
-f
option to force the move.
Examples
p4 move file1.c file2.c |
Assuming that |
p4 move //depot/d1/... //depot/d2/... |
Moving open files from directory |