p4 print

Synopsis

Syntax

Description

Any file in the depot can be printed, subject to permission limitations as granted by p4 protect. If the file argument does not map through the client view, you must provide it in depot syntax.

By default, the file is written with a header that describes the location of the file in the depot, the revision number of the printed file, and the number of the changelist that the revision was submitted under. To suppress the header, use the -q (quiet) flag.

Multiple file patterns can be included; all files matching any of the patterns are printed.

Options

-q	Suppress the one-line file header normally added by Perforce.
-o outfile	Redirect output to the specified output file on the local disk, preserving the same file type, attributes, and/or permission bits as the original file in the depot.
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	Yes	read

• p4 print's file arguments can take a revision range. Only the highest revision matched by any particular file is printed. If a file has no revisions within the specified range, is not printed.

• Because p4 print's output can be quite large when called with highly non-restrictive file arguments (for instance, p4 print //depot/... prints the contents of all files in the depot), it may be subject to a maxresults limitation as set in p4 group.

• In many cases, redirecting p4 print's output to a file via your OS shell will suffice.

The -o option is intended for users who require the automatic setting of file type and/or permission bits. This is handy for files such as UNIX symbolic links (stored as type symlink), files of type apple, automatically setting the execute bit on UNIX shell scripts stored as type text+x, and so on.

Related Commands

To compare the contents of two depot file revisions	p4 diff2
To compare the contents of an opened file in the client workspace to a depot file revision	p4 diff