rmmerge
Removes a merge arrow from an element's version tree
Applicability
Product |
Command type |
|---|---|
VersionVault |
cleartool subcommand |
Platform |
|---|
UNIX® |
|
Linux® |
Windows® |
Synopsis
- rmmerge [ –c/omment comment | –cfi/le comment-file-pname |–cq/uery
- | –cqe/ach | –nc/omment ] from-pname to-pname
Description
The rmmerge command deletes an existing merge arrow (a hyperlink of the predefined type Merge) between two versions of an element. Thus, this command is a specialized form of the rmhlink command. Both commands have an identical result; they differ only in the way you specify the merge arrow:
- With rmhlink, you specify the merge arrow itself, using a hyperlink selector.
- With rmmerge, you specify the versions linked by the merge arrow.
To list existing merge arrows, use the describe command, or use the find command with the hltype primitive. For example:
cmd-context describe util.c
version "util.c@@/main/3"
created 2007-04-05T17:01:12 by Allison (akp.user@starfield)
element type: text_file
Hyperlinks:
Merge@148@/usr/tmp/poolwk
/usr/tmp/poolwk/src/util.c@@/main/rel2_bugfix/1 ->
/usr/tmp/poolwk/src/util.c
Renaming the merge hyperlink type
Renaming the predefined hyperlink type for merge arrows does not defeat rmmerge. You specify the element's versions; rmmerge then determines the hyperlink type used for merge arrows in that element's VOB.
Restrictions
Identities
You must have one of the following identities:
- Element owner
- Element group member
- VOB owner
- root (UNIX® and Linux®)
- Member of the VersionVault administrators group (VersionVault on Windows®)
Locks
An error occurs if one or more of these objects are locked: VOB, element type, element, branch type, branch, hyperlink type.
Mastership
(Replicated VOBs only) Your current replica must master the hyperlink.
Options and arguments
Event records and comments
- Default
- Creates one or more event records, with commenting controlled by your .versionvault_profile file (default: –nc). See 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.
Specifying the versions
- Default
- None.
- from-pname, to-pname
- Extended pathnames of the versions connected by the merge arrow. The order in which you specify the versions is important: the source version first, the target version second.
Examples
The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include 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 UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
- Remove the merge arrow between the latest
version on the rel2_bugfix branch and the version of util.c in
the view.
cmd-context rmmerge util.c@@/main/rel2_bugfix/LATEST util.c
Removed merge from "util.c@@/main/rel2_bugfix/1" to "util.c".