Perforce Command Reference:   [Index]  [Prev] [Next]


p4 submit

Synopsis

Send changes made to open files to the depot

Syntax

p4 [g-opts] submit [file]
p4 [g-opts] -c changelist# submit
p4 [g-opts] -i submit

Description

When a file has been opened by p4 add, p4 edit, p4 delete,or p4 integrate, the file is listed in a changelist. The user's changes to the file are made only within in the client workspace copy until the changelist is sent to the depot with p4 submit.

By default, files are opened within the default changelist, but new numbered changelists can be created with p4 change. To submit the default changelist, use p4 submit; to submit a numbered changelist, use p4 submit -c changelist#.

When used with the default changelist, p4 submit brings up a form for editing in the editor defined by the EDITOR environment or registry variable. Files can be deleted from the changelist by deleting them from the form, but these files will remain open within the next default changelist. To close a file and remove it from all changelists, use p4 revert.

All changelists have a Status: field; the value of this field is pending or submitted. Submitted changelists have been successfully submitted with p4 submit; pending changelists have been created by the user but have not yet been submitted successfully.

p4 submit works atomically: either all the files listed in the changelist are saved in the depot, or none of them are.

p4 submit will fail if it is interrupted, or if any of the files in the changelist are not found in the client workspace, are locked within another client workspace, or require resolution and remain unresolved. If p4 submit fails while processing the default changelist, the changelist is assigned the next number in the changelist sequence, and the default changelist is emptied. The changelist that failed submission must be resubmitted by number after the problems are fixed.

A single file pattern may be specified as a parameter to a p4 submit of the default changelist. This file pattern is used to limit which files in the default changelist are included in the submission; files that don't match the file pattern are moved to the next default changelist.

Form Fields

Field Name Type Description
Change: Read-only Contains change number, or new if submitting the default change.
Client: Read-only Name of current client workspace.
User: Read-only Name of current Perforce user.
Status: Read-only value pending, submitted, or new. Not editable by the user. The status is new when the changelist is created; pending when its been created but has not yet been submitted to the depot with p4 submit, and submitted when its contents have been stored in the depot with p4 submit.
Description: Writable Textual description of changelist. This value must be changed.
Jobs: List A list of jobs that are fixed by this changelist. Controlled by ...(new job info here...). Jobs may be deleted from this list, but may not be added. This field will not appear if no there are no relevant jobs.
Files: List List of files being submitted in this changelist. Files may be deleted from this list, but may not be changed or added.

Options

-c changelist# Submit changelist number changelist#. Changelists are assigned numbers either manually by the user with p4 change, or automatically by Perforce when submission of the default changelist fails.
-i Read a changelist specification from standard input. Input must be in the same format at that used by the p4 submit form.
g_opts See global options.

Usage Notes

Can File Arg Use
Revision Specifier?
Can File Arg
Use Revision Range?
Minimal
Access Level Required
No No write

A file's location within the depot is determined by intersection of its locations in the client workspace with the client view as set within the p4 client form.

p4 submit's atomicity allows files to be grouped in changelists according to their purpose. For example, a single changelist might contain changes to three files that fix a single bug. Submission atomicity guarantees that all the files that fix the bug are stored in the depot at the same time.

When used with a numbered changelist, p4 submit will not display a form. To change the description information for a numbered changelist, use p4 change -c changelist#.

The file pattern parameter to p4 submit cannot be used when submitting a numbered changelist.

Examples

p4 submit Submit the default changelist. The user's revisions of the files in this changelist will be stored in the depot.
p4 submit -c 41 Submit changelist 41
p4 submit *.txt Submit only those files in the default changelist that have a suffix of .txt. Move all the other files in the default changelist to the next default changelist.

Related Commands

To create a new, numbered changelist

p4 change
To open a file in a client workspace and list it in a changelist p4 add
p4 edit
p4 delete
p4 integrate
To move a file from one changelist to another p4 reopen
To remove a file from all changelists, reverting it to its previous state p4 revert
To view a list of changelists that meet particular criteria p4 changes
To read a full description of a particular changelist p4 describe
To read files from the depot into the client workspace p4 sync
To edit the mappings between files in the client workspace and files in the depot p4 client



Perforce Command Reference:   [Index]  [Prev] [Next]


Copyright 1998 Perforce Software.
Contact us at [email protected]
Last updated: 06/14/98