integpb.html #1

<TITLE>Integrating Files via a Directory</TITLE>

<p> When you choose <b>Integrate...</b> from the <b>Action</b> menu on the <B>Files</B> 
  tab with a folder selected, you can use the resulting <a href="integrate?help">Integrate</a> 
  page to set up an integration to or from all the files in the selected path. 
  In most cases, you only need to be concerned with the following fields on the 
  <b>Integrate</b> page: 
<blockquote>

  <p><b>Current path: </b> This is initialized for you. If you change it, terminate 
    the pathname with a slash ("/"). 
  <p><b>Direction to integrate changes:
</b> 
Select the direction in which you want integrate:
  <ul>
    <p>
    <li><b>To files in current path</b> is the default. Files in the current path 
      are integration <i>targets</i>&#151;that is, they are the ones that will 
      be opened for integrate. Changes in the source files will be integrated 
      to files in the current path. 
      <p> 
      <p>
    <li><b>From files in current path</b> means the files in the current path 
      will be the integration <i>source</i> and will not themselves be opened 
      for integrate. Changes to files in the current path will be integrated to 
      the target files. 
  </ul>

<p><b>Use corresponding path:
</b> 
Enter a pathname here.
Make sure the pathname ends with a slash ("/").
This tells Perforce what pathname to use when looking for
corresponding source or target files,
depending on the integration direction you chose.

</blockquote>

<p> The "Integrate" button runs the <b>integrate</b> command and opens files for 
  integrate according to the options you choose. 
<p> You can use the "Preview Integration" button to see which files <i>would</i> 
  be opened. This is a particularly good idea when you are using <b>integrate</b> 
  to branch new files, to confirm that you are creating files in the correct path. 
  To actually run the <b>integrate</b> command after previewing it, click your 
  browser's "Back" button to return to the Integrate Options page, then click 
  "Integrate". 
<hr>
<h4>Advanced options</h4>

<p> An alternative to specifying corresponding paths each time you integrate is 
  to use a <a href="defs?help#branchview">branch spec</a>. A branch spec is a 
  predefined mapping of corresponding paths. To list branch specs, choose <b>Go 
  To>Branch List</b>. 
<blockquote>

  <p><b>Use branch spec: </b> Click this radio button and enter the name of the 
    branch spec. When you choose this option, any "corresponding path" you entered 
    above is ignored. 
  <ul>

<p>
    <li><b>Integrate files in current path:</b> Restricts the integration to the 
      files in the current path, using the branch spec. Whether the files in the 
      current path are the source or target files is controlled by the "direction 
      to integrate" option, above. 
      <p>
    <li><b>Integrate <u>all</u> files in branch spec:</b> If you chose this option, 
      the current path is ignored, and all the files in the branch spec are considered 
      for integration. You must choose whether to integrate in the forward or 
      reverse direction of the branch spec:<p> 
      <ul>
<p>
        <li><b>forward:</b> the files on the right-hand side of the branch spec 
          mapping are the targets and will be opened for integrate. The files 
          on the left-hand side of the branch spec mapping are the source. (default.) 
          <p>
        <li><b>reverse:</b> the files on the left-hand side of the branch spec 
          mapping are the targets and will be opened for integrate. The files 
          on the right-hand side of the branch spec mapping are the source. 
      </ul>

</ul>

</blockquote>

<p>
The remaining advanced options are the same regardless of how you arrived at
the <a href="integrate?help">Integrate</a> page.