p4 filelog

Synopsis

Syntax

Description

By default, the output consists of one line per revision in reverse chronological order. The format of each line is:

... #rev change chnum action on date by user@client (type) 'description'

• rev is the revision number;

• chnum is the number of the submitting changelist;

• action is the operation the file was open for: add, edit, delete, branch, import, or integrate;

If the action is import (that is, integrate from a remote depot) or integrate, Perforce displays a second line description, formatted as

... #integration-action partner-file

See p4 integrated for a full description of integration actions.

• date is the submission date (by default), or date and time (if the -t flag is used).

• user is the name of the user who submitted the revision;

• client is the name of the client workspace from which the revision was submitted;

• type is the type of the file at the given revision; and

• description is the first 30 characters of the corresponding changelist's description.

If the -l option is used, the description is the full changelist description as entered when the changelist was submitted. If the -L option is used, the description is the full changelist description, truncated to 250 characters.

Options

-i	Follow file history across branches. If a file was created by integration via p4 integrate, Perforce describes the file's revisions and displays the revisions of the file from which it was branched (back to the branch point of the original file).
-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.
-t	Display the time as well as the date.
-m maxrev	List only the first maxrev changes per file output.
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	No	list

• Because p4 filelog's output can be quite large when called with highly non-restrictive file arguments (for example, p4 filelog //depot/... displays the revision history for every file in the depot), p4 filelog commands may be subject to a maxresults limitation as set in p4 group.

• If both the -i and the -m maxrev flags are used, and a branch is encountered within the most recent maxrev revisions of the file, the most recent maxrev revisions of the file prior to the branch point are also displayed. p4 filelog -i follows branches down to a depth of 50 levels, which should be more than sufficient for any site.

• Old revisions of temporary object files (file type modifier +S, or tempobj) are displayed with an action of purge.

Examples

p4 filelog //depot/proj1/...	Display the revision history for every file under the depot's proj1 directory.
p4 filelog file1.c file1.h	Show the revision history for files file1.c and file1.h, which reside locally in the current working directory.

Related Commands

To read additional information about each file	p4 files
To display file information in a format suitable for scripts	p4 fstat
To view a list of open files	p4 opened
To view a list of files you've synced to your client workspace	p4 have