defs.html #1

<TITLE>Glossary</TITLE>


<TABLE BORDER=1 CELLPADDING=5>
  <TR> 
    <TD align=left valign=top><B><A NAME=hash>#</A></B></TD>
    <TD> Used in Perforce file patterns to indicate an absolute revision number. 
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=asterisk>*</A></B></TD>
    <TD> A wildcard used in Perforce file patterns to match files at the current 
      path level. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=dotdotdot>...</A></B></TD>
    <TD> A wildcard used in Perforce file patterns to match files at the current 
      path level and all levels below it. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=at>@</A></B></TD>
    <TD> Used in Perforce file patterns to indicate a symbolic revision identifier. 
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=absolute>absolute revision</A></B></TD>
    <TD> A revision number that identifies the ordinal version of a file. For 
      example, <code>foo.html#17</code> is the 17th version of <code>foo.html</code>. 
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=branch>branch</A></B></TD>
    <TD> To create new files with the <a href="integrate?help">integrate</a> command. 
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=branchspec>branch spec</A></B></TD>
    <TD> A stored branch view. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=branchview>branch view</A></B></TD>
    <TD> A mapping between two depot files or paths that defines their branching 
      relationship. Branch views control how the <a href="integrate?help">integrate</a> 
      command behaves when it is used to create new files, or to propagate changes 
      between files. (Sometimes also called a "branch spec." See above.) </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=changelist>changelist</A></B></TD>
    <TD> A record of a set of files changed at the same time. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=client>client</A></B></TD>
    <TD> The Perforce database entity that tracks your workspace and the files 
      synced to it. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=clientspec>client spec</A></B></TD>
    <TD> The specification of your workspace location, the depot files you plan 
      on working with, and where they will appear in your workspace. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=clientview>client view</A></B></TD>
    <TD> The subset of depot files you plan on working with in your client workspace. 
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=clientworkspace>client workspace</A></B></TD>
    <TD> The area on your local filesystem where you work on files managed by 
      Perforce. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=depot>depot</A></B></TD>
    <TD> A location in the master repository of files stored by the Perforce server. 
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=filepattern>file pattern</A></B></TD>
    <TD> The Perforce syntax for specifying a file or set files. May include wildcards 
      and/or revision specifiers. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=filelog>filelog</A></B></TD>
    <TD> The complete history of a file. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=headrevision>head revision</A></B></TD>
    <TD> The latest or "tip" revision of a file. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=job>job</A></B></TD>
    <TD> A Perforce database object that can be used to track defects, enhancements, 
      or other intended work. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=label>label</A></B></TD>
    <TD> 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. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=labelspec>label spec</A></B></TD>
    <TD> The specification that defines a label name and a label view. The label 
      spec creates the structure to build the label. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=labelview>label view</A></B></TD>
    <TD> The <i>label view</i> determines the depot files or paths that can be 
      associated with a particular label. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=labelsync>labelsync</A></B></TD>
    <TD> Performing a <i>labelsync</i> populates a label with files. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=metadata>metadata</A></B></TD>
    <TD> The data in a Perforce system that describes workspaces, file histories, 
      users, changelists, etc. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=openedfiles>opened files</A></B></TD>
    <TD> The files you are changing (editing, adding, deleting, etc.) in your 
      workspace. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=path>path</A></B></TD>
    <TD> A directory or folder. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=pendingchangelist>pending changelist</A></B></TD>
    <TD> A list of some or all of files open in your workspace. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=port>port</A></B></TD>
    <TD> The hostname and listen address that identifies the Perforce server (for 
      example, <tt>public.perforce.com:1666</tt>). </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=reviewdaemon>review daemon</A></B></TD>
    <TD> An optional program that the Perforce administrator can install to email 
      users when changelists are submitted by other users. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=helper>standard</A></B> (as in "<a href="helper?help">Standard 
      mode</a>") </TD>
    <TD> An instance of P4Web that can be used for workspace operations such as 
      opening files and submitting changlists (as opposed to viewer mode). See 
      <A NAME=browseonly HREF="index?help">Administering P4Web</a> for details.</TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=submit>submit</A></B></TD>
    <TD> The command that sends a pending changelist and contents of changed files 
      to the depot. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=submittedchangelist>submitted changelist</A></B></TD>
    <TD> A permanent record that is created when a pending changelist is submitted. 
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=symbolic>symbolic revision</A></B></TD>
    <TD> A revision symbol that identifies a file at a particular revision associated 
      the state of the depot. For example: 
      <UL>
        <P> 
        <LI><code>foo.html@1234</code> is the latest revision of <code>foo.html</code> 
          at the moment changelist 1234 was submitted, regardless of whether <code>foo.html</code> 
          was part of changelist 1234. 
          <P> 
        <LI><code>foo.html@2000/06/06</code> is the latest revision of <code>foo.html</code> 
          as of 00:00:00 hours, 06 June 2000. 
          <P> 
        <LI><code>foo.html@topaz</code> is the revision of <code>foo.html</code> 
          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 ambigous.) 
      </UL>
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=sync>sync</A></B></TD>
    <TD> The command that copies files from the depot to your workspace. (Short 
      for "synchronize.") </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=user>user</A></B></TD>
    <TD> The unique identifier of a Perforce user. (Usually the same as your login 
      name.) </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=userspec>user spec</A></B></TD>
    <TD> The specification describing various information associated with you 
      as a Perforce user, such as your full name and your email address. </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B>viewer</B> (as in <A NAME=browseonly HREF="browseonly?help">Viewer 
      mode</A>)</TD>
    <TD> An instance of P4Web that can be used only for browsing, and cannot perform 
      workspace operations.</TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=wildcard>wildcard</A></B></TD>
    <TD>Perforce uses three wildcards for pattern matching: "<b> * </b>", " <b>...</b> 
      ", and "%d". Any number and combination of these can be used in a single 
      string: 
      <ul>
        <li><b>*</b> matches anything except slashes; matches only within a single 
          directory. </li>
        <li><b>...</b> matches anything including slashes; matches across multiple 
          directories. </li>
        <li><b>%d</b> is used for parametric substitution in views. Matches strings 
          similarly to the <b>*</b> wildcard, but can be used to rearrange the 
          order of the matched substrings. </li>
      </ul>
    </TD>
  </TR>
  <TR> 
    <TD align=left valign=top><B><A NAME=workspace>workspace</A></B></TD>
    <TD> The area on your local filesystem where you work on files managed by 
      Perforce. (Also called a "client workspace.") </TD>
  </TR>
</TABLE>