p4 changes

List submitted and pending changelists.

The command p4 changelists is an alias for p4 changes.

Syntax

p4 [g-opts] changes [-i -t -l -L -f] [-c client] [ -e changelist#][-m max] 
                     [-r] [-s status] [-u user | --me] [[FileSpec][revSpec]]

Description

Use p4 changes to view a list of submitted and pending changelists. When you use p4 changes without any arguments, all numbered changelists are listed. (The default changelist is never listed.)

By default, the format of each line is:

Change num on date by user@client [status] description

If you use the -t option to display the time of each changelist, the format is:

Change num on datehh:mm:ss by user@client [status] description

The status value appears only if the changelist is pending or shelved. The description is limited to the first 31 characters unless you provide the -L option for the first 250 characters, or the -l option for the full description.

If you provide file patterns as arguments, the changelists listed are those that affect files matching the patterns, whether submitted or pending.

Revision specifications and revision ranges can be included in the file patterns:

To get a list all files within a range of revisions, include a revision range. For example, p4 jobs //...#20,52
To get a list of all changes from 1 to the specified revision, include a single revision specifier. For example, p4 jobs //...#20
To limit output to only those changelists made from the named client workspace or the named user, use the -c client or the -u user option
To limit output to only those changelists with the provided status (pending, shelved, or submitted) value, use the -s status option
To limit output to only changes that are greater or equal to the specified changelist number, use the -e changelist# option

In a distributed configuration, changes that are pending or shelved on an Edge Server are visible via the p4 changes command on other servers in the installation.

Administrators can use the -f option to view restricted changelists.

You can combine options and file patterns to limit the changelists that are displayed. You can also use the -m max option to limit output to max changes.

Tip

To reverse the order of the list so that the earliest changes appear before most recent changes, use the -r option.

The global -u global has a different meaning than the p4 changes -u option:

$ p4 -u bruno changes -u gale

where p4 -u bruno uses the global option to change the current user to bruno, and -u gale asks for a list of the changes that user gale made.

Options

`-c client`	List only changes made from the named client workspace
`-f`	View restricted changes (requires `admin` permission)
`-i`	Include changelists that affected files that were integrated with the specified files
`-l`	List long output, with the full text of each changelist description
`-L`	List long output, with the full text of each changelist description truncated at 250 characters
`-m max`	List only the highest numbered `max` changes.
`-r`	Reverse the order of the list, earliest first instead of most recent first
`-s status`	Limit the list to the changelists with the given status (`pending`, `submitted`, or `shelved`)
`-t`	Display the time as well as the date of each change
`-u user`	List only changes made from the named user
`--me`	Equivalent to -u $P4USER
`g-opts`	See Global Options

Usage Notes

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
Yes	Yes	`list`

If p4 changes is called with multiple file arguments, the sets of changelists that affect each argument are evaluated individually. The final output is neither combined nor sorted. The effect is the same as calling p4 changes multiple times, once for each file argument.
If files are not specified, p4 changes limits its report according to whether or not changes are public or restricted. Restricted submitted or shelved changes are not reported unless you either own the change or have list permission for at least one file in the change. Restricted pending (but unshelved) changes are visible only to the change owner.
p4 changes myfile#have accesses the db.have table lockless for the duration of the compute phase.

Examples

`p4 changes -m 5 //depot/project/...`	Show the last five submitted, pending, or shelved changelists that include any file under the `project` directory.
`p4 changes -m 5 -c eds_elm`	Show the last five submitted, pending, or shelved changelists from client workspace `eds_elm`.
`p4 changes -m 5 -s submitted -u edk`	Show the last five submitted changelists from user `edk`.
`p4 changes file.c@2010/05/01,2010/06/01`	Show any changelists that include file `file.c`, as mapped to the depot through the client view, during the month of May 2010.
`p4 changes -m 1 -s submitted`	Output a single line showing the changelist number of the last submitted changelist.
`p4 changes @2011/04/01,@now`	Show all changelists submitted from April 1, 2011 to the present.
`p4 changes @2011/04/01`	Show all changelists submitted before April 1, 2011.
`p4 changes -r -m 1 //depot/project/branch/...`	Show the first change on the specified branch.

Related Commands

To submit a pending changelist	`p4 submit`
To create a new pending changelist	`p4 change`
To read a detailed report on a single changelist	`p4 describe`