<TITLE>Creating and Editing Branch Specs</TITLE> <P> <P> <b>To create a new branch spec:</b> <P> <ol type=1> <li>Select the <b>Branches</b> tab. <li>Click the <b>Create branch spec</b> link at the top of the page. <li>Edit the fields as described <a href="editbranch?help#branchdesc">below</a>. <li>When you are finished, click the <b>Save</b> button. </ol> <P> <b>To edit a branch spec:</b> <p> <ol type=1> <li>Select the <b>Branches</b> tab. <li>Click on the name of the branch that you want to edit. <li>Select <b>Edit branch spec...</b> from the <b>Action</b> menu. <li>Edit the branch spec as desired, using the field descriptions <a href="editbranch?help#branchdesc">below</a>. <li>When you have finished editing the branch spec, click the <b>Save</b> button. </ol> <P><A NAME=branchdesc><B>Branch spec field descriptions</B></A> <br> The branch spec consists of the following fields: <table width="66%" border="1" cellpadding="1"> <tr> <td width="12%"><b>Field</b></td> <td width="88%"><b>Description</b></td> </tr> <tr> <td width="12%"><b>Branch</b></td> <td width="88%">The unique name of this branch spec. This cannot be edited. </td> </tr> <tr> <td width="12%"><b>Update</b></td> <td width="88%">Date that this branch spec was last changed. This field cannot be edited</td> </tr> <tr> <td width="12%"><b>Access</b></td> <td width="88%">Shows when this branch spec was last accessed. This field cannot be edited. </td> </tr> <tr> <td width="12%"><b>Owner</b></td> <td width="88%">The user who owns this branch spec. By default, this is the user who created the branch. </td> </tr> <tr> <td width="12%"><b>Description</b></td> <td width="88%">Optional information that can be used to describe this branch spec's purpose. </td> </tr> <tr> <td width="12%"><b>Options</b></td> <td width="88%"> <ul> <li><b>Only allow owner to change branch spec <i>(locked)</i></b> <br> Can either be locked or unlocked. If the checkbox is selected, the branch spec is locked, and only the owner (as specified in the <b>Owner</b> field) can modify the branch spec. The branch spec cannot be deleted until it is unlocked. <li><b>Use indirect integration history to find base <i>(indirect)</i> </b> <br> Usually, you cannot integrate changes if there is no prior history between the source and target (since there is no way to identify the base for the merges). Selecting this option searches for indirect history through intermediate files. If there is still no history, the last revision of source file that was opened for add is used as the base (this is almost always the first revision of source file). </ul> </td> </tr> <tr> <td width="12%"><b>View</b></td> <td width="88%">A set of mappings from one set of files in the depot (the source files) to another set of files in the depot (the target files). The view maps from one location in the depot to another. <p> For example, the branch view: <p> <table border=1 cellpadding=5 width=300> <tr> <td><kbd>//depot/main/... //depot/r2.1/...</kbd></td> </tr> </table> <p> maps all the files under <tt>//depot/main</tt> to <tt>//depot/r2.1 </tt> </td> </tr> </table>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 12234 | Matt Attaway |
Rejigger P4Web project in preparation for official sunsetting The bin directory contains the last official builds of P4Web from the Perforce download site. P4Web is soon to be completely sunsetted; these builds are here for folks who don't want to build their own. To better handle the archived builds the source code has been moved into a separate src directory. |
||
//guest/perforce_software/p4web/Help/editbranch.html | |||||
#1 | 8914 | Matt Attaway | Initial add of the P4Web source code |