Perforce Command Reference: [Index] [Prev] [Next]

p4 filelog

Synopsis

Print detailed information about files' revisions

Syntax

p4 [g-opts] filelog -l file...

Description

p4 filelog describes each revison of the files provided as arguments. At least one file or file pattern must be provided as an argument. The output lists one line per revision; the format of each line is:

... #rev change chnum op on date by usr@client (type) 'descrip'

where

rev is the revision number;
chnum is the number of the submitting changelist;
op is the operation the file was open for: add, edit, delete, branch, or integrate;
date is the submission date and time;
usr is the name of the user who submitted the revision;
client is the name of the client workspace the revision was submitted from;
type is the file type of the file at the given revision; and
descrip is the first 30 characters of the corresponding changelist's description.

At least one file or file pattern must be provided.

Options


`-l`	List the full description of each revision.
`g_opts`	See global options section.

Usage Notes


Can File Arg Use Revision Specifier?	Can File Arg Use Revision Range?	Minimal Access Level Required
No	No	`list`

Since p4 filelog's output can be quite large when called with highly non-restrictive file arguments (e.g., p4 filelog //depot/... will print the revision history for every the files in the depot), it may be subject to a maxresults limitation as set in p4 group.

Examples


`p4 -c foo filelog //depot/...`	Display the revision history for every file under the depot's `proj1` directory in client workspace `foo`.
`p4 filelog bar baz`	Show the revision history for files `bar` and `baz`, which reside locally in the current working directory.

Related Commands


To read additional information about each file	`p4 files`
To view a list of open files	`p4 opened`
To view a list of files you've synced to your client workspace	`p4 have`

Perforce Command Reference: [Index] [Prev] [Next]