rmbranch

Removes a branch from the version tree of an element

APPLICABILITY

ClearCase (cleartool subcommand), Attache (command)

SYNOPSIS

rmbranch [ -c·omment comment | -cfi·le comment-file-pname |-cq·uery

| -cqe·ach | -nc·omment ]
[ -f·orce ] pname ...

DESCRIPTION

This command destroys information irretrievably. Using it carelessly may compromise your organization's ability to support old releases.

The rmbranch command deletes one or more branches from their elements. For each branch, deletion entails the following:

• Removal from the entire branch structure from the VOB database: branch object and version objects
• Removal of all metadata items (labels, attributes, hyperlinks, and triggers) that were attached to the deleted objects
• Removal of all event records for the deleted objects
• (File elements only) Removal of the data containers that hold the deleted versions' file-system data
• Creation of a destroy sub-branch event record for the parent branch of the deleted branch

NOTE: If all of an element's versions are stored in a single data container, the deleted versions are removed logically, not physically.

To delete all instances of a branch and the branch type object, use the rmtype command.

Restrictions

You cannot delete these branches:

• A branch that is checked out
• An element's main branch
• A branch from which someone has checked out elements (see the reference page for uncheckout)

PERMISSIONS AND LOCKS

Permissions Checking: For each object processed, you must be one of the following: branch creator, element owner, VOB owner, or member of the ClearCase group. See the permissions reference page.

Locks: An error occurs if any of the following objects are locked: VOB, element type, element, branch type, branch, pool (nondirectory elements only).

OPTIONS AND ARGUMENTS

EVENT RECORDS AND COMMENTS. Default: Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: -nc). See CUSTOMIZING COMMENT HANDLING in the comments reference page. Comments can be edited with chevent.

-c·omment comment | -cfi·le comment-file-pname |-cq·uery | -cqe·ach | -nc·omment

Overrides the default with the option you specify. See the comments reference page.

CONFIRMATION STEP.  Default: rmbranch prompts for confirmation before deleting anything.

-f·orce

Suppresses the confirmation step.

SPECIFYING THE BRANCHES TO BE REMOVED.  Default: None.

pname ...

One or more VOB-extended pathnames, indicating the branches to be deleted. Examples:

foo.c@@\main\bugfix
\proj1\include\proj.h@@\main\temp_482

EXAMPLES

Examples including wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.

In cleartool single-command mode, cmd-context represents the command interpreter prompt. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.

• Delete the maintenance branch of element util.c.

cmd-context rmbranch util.c@@\main\maintenance

Branch "util.c@@\main\maintenance" has 0 sub-branches, 2 sub-versions
Remove branch, all its sub-branches and sub-versions? [no] yes
Removed branch "util.c@@\main\maintenance".

• Verify, with the lsvtree command, that element msg.c has a patch2 branch. Then, delete that branch without prompting for confirmation.

cmd-context lsvtree -branch \main\patch2 msg.c

msg.c@@\main\patch2
msg.c@@\main\patch2\1

cmd-context rmbranch -force msg.c@@\main\patch2

Removed branch "msg.c@@\main\patch2".

SEE ALSO

lsvtree, mkbranch, mkbrtype, rmtype, rmver