change -- Create or edit a changelist description
p4 change [ -f -s ] [ changelist# ]
p4 change -d [ -f -s ] changelist#
p4 change -o [ -s ] [ changelist# ]
p4 change -i [ -f -s ]
'p4 change' creates and edits changelists and their descriptions.
With no argument, 'p4 change' creates a new changelist. If a
changelist number is given, 'p4 change' edits an existing, pending
changelist. In both cases the changelist specification is placed
into a form and the user's editor is invoked.
The -d flag discards a pending changelist, but only if it has no
opened files and no pending fixes associated with it.
Use p4 opened -a to report on opened files and p4 reopen to move them
to another changelist.
Use p4 fixes -c changelist# to report on
pending fixes and p4 fix -d -c changelist# jobs... to delete
pending fixes. The changelist can only be deleted by the user and
client who created it, or by a superuser using the -f flag.
The -o flag causes the changelist specification to be written
to the standard output. The user's editor is not invoked.
The -i flag causes a changelist specification to be read from the
standard input. The user's editor is not invoked.
The -f flag allows the superuser to update or delete other users'
pending changelists. -f also allows the superuser to delete
submitted changelists once they have been emptied of files via
p4 obliterate Normally, submitted changelists are immutable.
The -s flag extends the list of jobs to include the fix status
for each job. On new changelists, the fix status begins as the
special status 'ignore', which if left unchanged simply excludes
the job from those being fixed. Otherwise, the fix status, like
that applied with p4 fix -s becomes the job's status when
the changelist is committed. Note that this option is not meant
for end-users. It exists to support propagating information from
an external defect tracking system.