Inclusion List

When RIN List Type is defined to be 'I' or ‘i’, then RIN_list represents a inclusion list. When there is no inclusion list (the list is unpopulated) then there are no inclusions and all commands that match the associated operation are still ignored; when the list is populated, only instances that match the inclusion will apply.

Any number of inclusions may be placed in the inclusion list. There can be an inclustions on any of the metadata types: attributes, branches, elements, hyperlinks, labels and triggers as wel as certain UCM Data Types: attributes, components, folders, projects and streams (ClearTrigger supports matching on activities and folders even though native ClearCase does not). If the RIN_type is ‘I’, “full matching” applies and restrictions of the same type are ORed together and restrictions of different types are ANDed together before the restriction is tested. If the RIN_type is ‘i’, “single matching” applies and all restrictions of any type are ORed together before the restriction is tested.

The format for this section is a list of zero or more type selections of the form type<name> where type is from:
Base typeUCM type
  • attype
  • brtype
  • eltype
  • hltype
  • lbtype
  • trtype
  • activity
  • component
  • folder
  • project
  • stream
and name is an implicit name like "REL1.9", "integration" or a pattern to match several or a few type instances. You may use ~alias names to identify large of often used series of type selections.
Example Typeexample
attribute; attype<QA_State> ;
branch; brtype<integration> ;
element; eltype<c_source> ;
hyperlink; hltype<merge> ;
label; lbtype<BETA> ;
trigger; trtype<no_co> ;
UCM activity; activity<bug_152> ;
UCM component; component<\comp1> ;
UCM folder; folder<a_folder> ;
UCM project; project<project_z> ;
UCM stream; activity<feature_x> ;
patterns; lbtype<REL#.#_*> brtype<*_int_*> ;
patterns; attype<CR##?_*> trtype<*> ;
aliases; ~protected_labels ~restricted_braches ;

See also: Restriction List, Negation List