p4 print

Print the contents of a depot file revision.

Syntax conventions

p4 [g-opts] print [-a -A -K -q] [-m max] --offset bytesToSkip --size bytesToPrint 
    [-o outfile] FileSpec[revSpec]
p4 [g-opts] print -U unload FileSpec

Description

The p4 print command writes the contents of a depot file to standard output. However, options permit printing only a portion of a file, printing multiple versions of a file, printing multiple files, or printing to an output file.

If a revision range is included, by default, only the highest revision in that range is printed. See Using revision ranges.

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

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) option.

By default, RCS keywords are expanded. To suppress keyword expansion, use the -k (keyword) option.

By default, the local depot is searched for the specified file. If you specify the -U option, the unload depot is searched instead.

Options

-a

For each file, print all revisions within a specified revision range, rather than only the highest revision in the range.

-A

Attempt to print a file stored in an archive depot.

-K

Suppress RCS keyword expansion.

-m max

Print only the first max files.

--offset bytesToSkip (Optional) Skip the specified number of bytes and only print what follows. Can be used with --size.
--size bytesToPrint (Optional) Print the specified number of bytes from the offset. If --offset is not explicitly set, prints the specified number of bytes from the beginning of the file.

-o outfile

Redirect output to the specified output file (outfile) on the local disk.

This preserves the same file type, attributes, and/or permission bits as the original file (FileSpec) in the depot.

Multiple files can be written by using wildcards in the localFile argument that match wildcards in the depot (FileSpec) argument.

For example:

To print the contents of a directory and directories under that directory, use the ... wildcard:

$ p4 print -o c:/tmp/main-copy/... //depot/main/...

To print all files that match readme.txt or readme.pdf, you might specify

$ p4 print -o readme.* //depot/readme.*

-q

Suppress the one-line file header normally added by Helix Server.

-U

Look for the specified file or files in the unload depot. Data about an unloaded client, label, or task stream can be printed.

g-opts

See Global options.

Usage Notes

Can File Arguments Use Revision Specifier? Can File Arguments Use Revision Range? Minimal Access Level Required

Yes

Yes

read

  • Because most terminals are unable to display UTF16 content, the default behavior of the p4 print command is to return UTF8 content. You can override this behavior by bypassing terminal output entirely and specifying an output file, for example:

    $ p4 print -q -o   //depot/file

    If your terminal supports UTF16 output, specify standard output as the output file:

    $ p4 print -q -o - //depot/file
  • p4 print's file arguments can take a revision range. By default, only the highest revision matched by any particular file is printed (that is, when no range is specified, the implied range is #1,#head, and the highest revision is #head). To print all files in a specified (or implied) range, use the -a option.
  • 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 useful for files such as symbolic links (stored as type symlink), automatically setting the execute bit on UNIX shell scripts stored as type text+x, and files of type apple .

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