Perforce 2002.2 Command Reference | ||
<< Previous Chapter p4 dirs |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 filelog |
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.
If p4 edit is run on any files that are already opened for edit, these files are simply moved into the specified changelist, which must have a status of pending.
-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. |
See the Global Options section. |
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.
Perforce 2002.2 Command Reference | ||
<< Previous Chapter p4 dirs |
Table of Contents Index Perforce on the Web |
Next Chapter >> p4 filelog |