p4 filelog

Perforce 2000.2 Command Reference (2000.2.cr.1)


<< Previous Chapter p4 edit	Table of Contents Index Perforce on the Web	Next Chapter >> p4 files

Print detailed information about files' revisions

p4 [g-opts] filelog [-i] [-l] [-m maxrev] file...

p4 filelog describes each revision 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 in reverse chronological order; the format of each line is:

rev

chnum

action

date

user

client

type

description

where:

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, or integrate;
date is the submission date;
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
descrip is the first 30 characters of the corresponding changelist's description.

If the action is integrate, Perforce displays a second line, formatted as

integration-action partner-file

See p4 integrated for a full description of integration actions.

`-i`	Follow file history across branches. If a file was created by integration via `p4 integrate`, Perforce will describe the file's revisions and display the revisions of the file it was branched from (back to the branch point of the original file).
`-l`	List the full description of each revision
`-m maxrev`	List only the first `maxrev` changes per file output.
`g_opts`	See the Global Options section.

Can File Arguments Use Revision Specifier?	Can File Arguments Use Revision Range?	Minimal Access Level Required
Yes	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 file in the depot), it 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 the file prior to the branch point will also be displayed. p4 filelog -i will follow branches down to a depth of 50 levels, which should be more than sufficient for any site.

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

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`