Previous Table of Contents Index Next
Perforce 2009.1: Command Reference



p4 filelog
Synopsis
Print detailed information about files' revisions.
Syntax
p4 [g-opts] filelog [ -h -i -l -L -t -m maxrev ] file...
Description
p4 filelog describes each revision of the files provided as arguments. At least one file or file pattern must be provided as an argument.
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'
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, 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
Display file content history instead of file name history. The revisions that are listed include revisions of other files that were branched/copied (using p4 integrate and p4 resolve -at) to the specified revision. Revisions that were replaced by copying or branching are not displayed, even if they are in the history of the specified revision.
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).
-m maxrev
List only the first maxrev changes per file output.
Usage Notes
Can File Arguments Use
Revision Specifier?
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 +Sn) are displayed with an action of purge.
Examples
Show the revision history for files file1.c and file1.h, which reside locally in the current working directory.
Related Commands


Previous Table of Contents Index Next

Perforce 2009.1: Command Reference
Copyright 1999-2009 Perforce Software.