p4 have
Synopsis
List files and revisions that have been synced to the client workspace.
Syntax
p4 [g-opts
] have
[file
...]
Description
List those files and revisions that have been copied to the client
workspace with p4 sync
. If file patterns are provided,
the list is limited to those files that match one of the patterns, and
to those files that are mapped to the client view.
p4 have
lists the files, one per line, in the format:
depot-file
#revision-number
- local-path
depot-file
is the path to the file in depot syntax.revision-number
is the have revision; the revision presently in the current client workspacelocal-path
is the path as represented in terms of the local filesystem (that is, in local syntax).
Options
|
See “Global Options”. |
Usage Notes
Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
---|---|---|
No |
No |
|
-
Some Perforce documentation refers to a client workspace’s have list. The have list is the list of files reported by
p4 have
, and is the list of file revisions that have been most recently synced from the depot.The have list does not include files that exist in your client workspace but not in the depot (nor does it include files at deleted revisions.)
For instance, if you use
p4 add
to open a newly created file in your client workspace for add, or if you usep4 integrate
to create a group of files in your client workspace, but haven’t submitted them, the new files do not appear in the output ofp4 have
.The set of all files in your client workspace is the union of the set of files listed by
p4 have
with the set of files listed byp4 opened
. -
For files containing the special characters
@
,#
,*
, and%
, thedepot-file
field shows the ASCII expression of the character’s hexadecimal value, and thelocal-path
shows the special character. For example://depot/status/100%25.txt#1 - /staff/status/100%.txt
Examples
p4 sync //depot/name... p4 sync //depot/name/...#4 |
In each of these two pairs of commands: The first The second |