| # |
Used in Perforce file patterns to indicate an absolute revision number.
|
| * |
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. |
| @ |
Used in Perforce file patterns to indicate a symbolic revision identifier.
|
| 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 |
To create new files with the integrate command.
|
| 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 that tracks 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 you plan on working with in your client workspace.
|
| 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. |
| filelog |
The complete history of a file. |
| head revision |
The latest or "tip" revision of a file. |
| job |
A Perforce database object that can be used to track defects, enhancements,
or other intended work. |
| label |
Provides a means for marking a particular set of file revisions for later
access. At any subsequent time, the label can be used to copy old file revisions
into a client workspace. |
| label spec |
The specification that defines a label name and a label view. The label
spec creates the structure to build the label. |
| label view |
The label view determines the depot files or paths that can be
associated with a particular label. |
| labelsync |
Performing a labelsync populates a label with files. |
| 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. |
| path |
A directory or folder. |
| pending changelist |
A list of some or all of files open in your workspace. |
| port |
The hostname and listen address that identifies the Perforce server (for
example, 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. |
| standard (as in "Standard
mode") |
An instance of P4Web that can be used for workspace operations such as
opening files and submitting changelists (as opposed to viewer mode). See
Administering P4Web for details. |
| 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:
foo.html@1234 is the latest revision of foo.html
at the moment changelist 1234 was submitted, regardless of whether foo.html
was part of changelist 1234.
foo.html@2000/06/06 is the latest revision of foo.html
as of 00:00:00 hours, 06 June 2000.
foo.html@topaz is the revision of foo.html
currently in either the "topaz" client workspace or in the "topaz" label.
(Because labels and clients can't have the same names, this situation
is not ambiguous.)
|
| 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 Viewer
mode) |
An instance of P4Web that can be used only for browsing, and cannot perform
workspace operations. |
| wildcard |
Perforce uses three wildcards for pattern matching: " * ", " ...
", and "%d". Any number and combination of these can be used in a single
string:
- * matches anything except slashes; matches only within a single
directory.
- ... matches anything including slashes; matches across multiple
directories.
- %d is used for parametric substitution in views. Matches strings
similarly to the * wildcard, but can be used to rearrange the
order of the matched substrings.
|
| workspace |
The area on your local filesystem where you work on files managed by
Perforce. (Also called a "client workspace.") |