(Hint: Use your browser's "Find" to look up words in this page.)
| # | Used in Perforce file patterns to indicate an absolute revision number. |
| @ | Used in Perforce file patterns to indicate a symbolic revision identifier. |
| * | A wildcard used in Perforce file patterns to match files at the current path level. |
| ... | A wildcard used in Perforce file patterns to match files at the current path level and all levels below it. |
| absolute revision |
A revision number that identifies the ordinal version of a file.
For example, foo.html#17 is the 17th version of foo.html.
|
| branch | A codeline that was created by copying another codeline, as opposed to a codeline that was created by adding original files. |
| branch spec | A stored branch view. |
| branch view | A mapping between two depot files or paths that defines their branching relationship. Branch views control how the integrate command behaves when it is used to create new files, or to propagate changes between files. (Sometimes also called a "branch spec." See above.) |
| changelist | A record of a set of files changed at the same time. |
| client | The Perforce database entity uniquely associated with your workspace and the files synced to it. |
| client spec | The specification of your workspace location, the depot files you plan on working with, and where they will appear in your workspace. |
| client view | The subset of depot files to be worked on by a client. This view is specified in the client view of the client specification. |
| client workspace | The area on your local filesystem where you work on files managed by Perforce. |
| depot | A location in the master repository of files stored by the Perforce server. |
| file pattern | The Perforce syntax for specifying a file or set files. May include wildcards and/or revision specifiers. |
| head revision | The latest or "tip" revision of a file. |
| helper (as in "P4Web Helper") | A private P4Web that can be used for workspace operations as well as for browsing Perforce depot files and metadata. |
| job | A defect, enhancement or other unit of intended work. |
| label | A symbolic name used to refer to a set of files at specific revisions. |
| label spec | The specification that defines a label name and a label view. |
| label view | The depot files or paths that can be associated with a particular label. |
| metadata | The data in a Perforce system that describes workspaces, file histories, users, changelists, etc. |
| opened files | The files you are changing (editing, adding, deleting, etc.) in your workspace. |
| pending changelist | A list of some or all of files open in your workspace. |
| path | A directory or folder. |
| port | The hostname and listen address that identifies the Perforce server (e.g, "public.perforce.com:1666"). |
| review daemon | An optional program that the Perforce administrator can install to email users when changelists are submitted by other users. |
| submit | The command that sends a pending changelist and contents of changed files to the depot. |
| submitted changelist | A permanent record that is created when a pending changelist is submitted. |
| symbolic revision |
A revision symbol that identifies a file at a particular revision associated
the state of the depot.
For example:
|
| sync | The command that copies files from the depot to your workspace. (Short for "synchronize".) |
| user | The unique identifier of a Perforce user. (Usually the same as your login name.) |
| user spec | The specification describing various information associated with you as a Perforce user, such as your full name and your email address. |
| viewer (as in P4Web Viewer) | A public P4Web that is used only for browsing. |
| workspace | The area on your local filesystem where you work on files managed by Perforce. (Also called a "client workspace.") |