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]]
[--stream | --nostream]
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
You can combine options and file patterns to limit the changelists that are displayed.
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 limit output to only those changelists made from the named client workspace or the named user, use the
-c clientor the-u useroption - To limit output to only
those changelists with the provided
status(pending,shelved, orsubmitted) value, use the-s statusoption. - To limit output to only
changes that are greater or equal to the specified changelist
number, use the
-e changelist#option
In a multi-server 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.
status
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 specify //... or any other path or revision specifier, the output includes only submitted changes. If you want to see pending or shelved changes when using //... or any other path or revision specifier, add the -s status option: -s pending or -s shelved. For example, p4 changes -s pending //depot/project1/...#3
Limit output with -m max
You can also use the -m
max option to limit output to
max changes:
p4 changes -m 5 shows the five most recent changes.
To reverse the order of the list so that the earliest changes appear before the most recent changes, use the -r option:
p4 changes -r -m 5 shows the five oldest changes.
time
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
Global -u versus p4 changes -u
The global -u in Global options has a different meaning than the p4 changes -u option:
$ p4 -u maria changes -u linda
where p4 -u maria uses the global option to change the current user to maria, and -u linda asks
for a list of the changes that user linda made.
Options
|
|
List only changes made from the named client workspace |
|
|
Display only changes where the changelist number is equal to, or higher than, the specified changelist number |
|
|
View restricted changes (requires |
|
|
Include changelists that affected files that were integrated with the specified files |
|
|
List long output, with the full text of each changelist description |
|
|
List long output, with the full text of each changelist description truncated at 250 characters |
|
|
List only the highest numbered |
-r
|
Reverse the order of the list, earliest first instead of most recent first |
|
|
Limit the list to the changelists with the specified status
: If you specify |
|
|
Display the time (hour:minute:second) after the date (yyyy/mm/dd) of each change. Without |
|
|
List only changes made from the named user |
--stream
|
Displays only changes that contain a stream spec |
--nostream
|
Displays only changes that do not contain a stream spec |
|
|
Equivalent to -u $P4USER |
|
|
See Global options |
Usage Notes
| Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
Command Alias |
|---|---|---|---|
|
Yes |
Yes |
|
p4 changelists
|
- If
p4 changesis 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 callingp4 changesmultiple times, once for each file argument. - If files are not specified,
p4 changeslimits its report according to whether or not changes are public or restricted. Restrictedsubmittedorshelvedchanges are not reported unless you either own the change or havelistpermission for at least one file in the change. Restrictedpending(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.
-
The command returns no output if there is no object to report on.
Examples
| p4 changes file.c#3 | Show the changelists associated with file versions #1, #2, and #3. |
| p4 changes file.c#3,6 | Show the changelists associated with file versions #3, #4, #5, and #6. |
| p4 changes -e 800 file.c | Show the changelists that are greater or equal to changelist number 800 |
|
|
Show the last five submitted changelists
that include any file under the |
|
|
Show the last five submitted, pending, or shelved changelists
from client workspace |
|
|
Show the last five shelved changelists from user
|
|
|
Show any changelists that include file |
|
|
Output a single line showing the changelist number of the last submitted changelist. |
|
|
Show all changelists submitted from the specified date to the present. |
|
|
For changelists that are submitted, show all changelists submitted before the specified date. For changelists that are pending or shelved, show all changelists created before the specified date. |
|
|
Show the first (oldest) change on the specified branch. |
p4 changes -t -m 25
|
Show the last five submitted and pending changelists with time format showing full timestamp of yyyy/mm/dd hour:minute:second |
Related Commands
|
To submit a pending changelist |
|
|
To create a new pending changelist |
|
|
To read a detailed report on a single changelist |






