p4 edit

Synopsis

Syntax

Description

Perforce controls the local OS file permissions; when p4 edit is run, the OS write permission is turned on for the specified files.

When a file that has been opened for edit with p4 edit is submitted to the depot, the file revision that exists in the depot is not replaced. Instead, the new file revision is assigned the next revision number in sequence, and previous revisions are still accessible. By default, the newest revision (the head revision) is used by all commands that refer to the file.

By default, the specified files are added to the default changelist. Use -c to specify a different changelist.

To move files already opened for edit from one changelist to another, use p4 reopen.

Options

-c change#	Opens the files for edit within the specified changelist. If this flag is not provided, the files are linked to the default changelist.
-t type	Stores the new file revision as the specified type, overriding the file type of the previous revision of the same file. See the File Types section for a list of file types.
-n	Preview which files would be opened for edit, without actually changing any files or metadata.
g-opts	See the Global Options section.

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
No	No	open

1. Use p4 edit to open the file in the client workspace,

2. Edit the file with any editor,

3. Submit the file to the depot with p4 submit.

By default, Perforce does not prevent users from opening files that are already open; its default scheme is to allow multiple users to edit the file simultaneously, and then resolve file conflicts with p4 resolve. To determine whether or not another user already has a particular file opened, use p4 opened -a file.

If you need to prevent other users from working on files you've already opened, you can either use the p4 lock command (to allow other users to edit files you have open, but prevent them from submitting the files until you first submit your changes), or you can use the +l (exclusive-open) filetype to prevent other users from opening the files for edit at all.

In older versions of Perforce, p4 edit was called p4 open.

Examples

p4 edit -t text+k doc/*.txt	Opens all files ending in .txt within the current directory's doc subdirectory for edit. These files are linked to the default changelist; these files are stored as type text with keyword expansion.
p4 edit -t +l //depotname/...	Implements pessimistic locking (exclusive-open) for all files in a depot. After this changelist is submitted, only one user at a time will be able to edit files in the depot named depotname.
p4 edit -c 14 ...	Opens all files anywhere within the current working directory's file tree for edit. These files are examined to determine whether they are text or binary, and changes to these files are linked to changelist 14.
p4 edit status%40jan1.txt	Open a file named [email protected] for edit. For details about how to specify other characters reserved for use as Perforce wildcards, see "Limitations on characters in filenames and entities" on page 250.

Related Commands

To open a file for add	p4 add
To open a file for deletion	p4 delete
To copy all open files to the depot	p4 submit
To copy files from the depot into the client workspace	p4 sync
To create or edit a new changelist	p4 change
To list all opened files	p4 opened
To revert a file to its unopened state	p4 revert
To move an open file to a different changelist or change its filetype	p4 reopen