p4 changes

Synopsis

Syntax

Description

The format of each line is:

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

If you provide file patterns as arguments, the changelists listed are those that affect files matching the patterns. Only submitted changelists will be reported in this instance; pending changelists (by definition) have not yet affected any files in the depot.

Revision specifications and revision ranges can be included in the file patterns. Including a revision range lists all changes that affect files within the range; providing a single revision specifier lists all changes from 1 to the specified revision.

The -s status flag is used to limit output to only those changelists with the provided status (pending or submitted) value.

You can combine flags and file patterns to substantially limit the changelists that are displayed. Additionally, the -m maxnum flag can be used to further limit output to maxnum changes.

Options

-i	Include changelists that affected files that were integrated with the specified files.
-l	Provide long output that includes the full descriptions of each changelist
-m maxnum	List only the highest-numbered maxnum changes.
-s status	Limit the list to the changelists with the given status (pending or submitted)
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
Yes	Yes	list

Examples

p4 changes -m 5 //depot/fooproj/...	Show the last five submitted changelists that included any file under the fooproj directory
p4 changes bar@1998/05/01,1998/06/01	Show any changelists that included file bar, as mapped to the depot through the client view, during the month of May, 1998.
p4 changes -m 1 -s submitted	Output a single line showing the changelist number of the last submitted changelist.

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