p4 move

Move (rename) a file from one location to another.

Syntax

p4 [g-opts] move [-c change] [-f -n -k] [-t filetype] fromFiletoFile

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

`-c change`	If a changelist number is provided, the files are opened in the numbered pending changelist.
`-t filetype`	If a filetype is specified, the file is reopened as the new filetype.
`-f`	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.
`-k`	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.
`-n`	Preview the move that would be performed, without actually moving files.
`g-opts`	See Global Options.

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
`fromFile`: Yes `toFile`: No	No	`read` access for `fromFile` `write` access for `toFile`

Files must be open for add or open for edit 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 `file1.c` is open for add or edit, move `file1.c` to `file2.c`.
`p4 move //depot/d1/... //depot/d2/...`	Moving open files from directory `d1` to directory `d2`.