|
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 workspace
- local-path is the path as represented in terms of the local filesystem (i.e., in local syntax).
Usage Notes
Can File Arguments Use
Revision Specifier?
|
Can File Arguments Use
Revision Range?
|
Minimal Access Level Required
|
|---|
|
No
|
No
|
list
|
- 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. It does not include files that exist in your client workspace but not in the depot.
- For instance, if you use p4 add to open a newly created file in your client workspace for add, or if you use p4 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 of p4 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 by p4 opened.
Examples
|
p4 sync //depot/foo...
p4 have //depot/foo
p4 sync //depot/foo/...#4
p4 have //depot/foo
|
In each of these two pairs of commands:
The first p4 have shows that the highest revision of the file has been copied to the client workspace.
The second p4 have shows that the fourth revision is the revision currently in the client workspace.
|
Related Commands
|
To copy file revisions from the depot to the client workspace
|
p4 sync
|
|