Creating and Editing Branch Specs

To create a new branch spec,

1. Select the Branches tab.
2. Click the Create branch spec link at the top of the page.
3. Edit the fields as described below.
4. When you are finished, click the Save button.

To edit a branch spec,

1. Select the Branches tab.
2. Click on the name of the branch that you want to edit.
3. Select Edit branch spec... from the pulldown menu.
4. Edit the branch spec as desired, using the field descriptions below.
5. When you have finished editing the branch spec, click the Save button.

Branch spec field descriptions
The branch spec consists of the following fields:

Branch:

The unique name of this branch spec. This cannot be edited.

Update:

Shows when this branch spec was last changed. This field cannot be edited.

Access:

Shows when this branch spec was last accessed. This field cannot be edited.

Owner:

The user who "owns" this branch spec. By default, this is the user who created the branch.

Description:

Optional information that can be used to describe this branch spec's purpose.

Options:

• Only allow owner to change branch spec (locked)
  Can either be locked or unlocked. If the checkbox is selected, the branch spec is locked, and only the owner (as specified in the Owner field) can modify the branch spec. The branch spec cannot be deleted until it is unlocked.
• Use indirect integration history to find base (indirect)
  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).

View:

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.

For example, the branch view:

//depot/main/... //depot/r2.1/...

will map all the files under: //depot/main to //depot/r2.1