The Default Group of a Workspace or Stream
How Elements Become Members of the Default Group
How Elements are Removed from the Default Group
For each dynamic stream A stream whose configuration changes over time, with new versions promoted from child workspaces and/or from other dynamic streams. It also inherits versions from its parent stream. and workspace A location in which one or more users perform their work, using files under version control. Each workspace consists of a workspace stream in the repository, and a workspace tree in the user’s disk storage. (but not for pass-through streams When a version is nominally promoted to pass-through stream X, the version automatically 'passes through' X: it is actually promoted to X's parent stream., snapshots An immutable (frozen, static) stream that captures the configuration of another stream at a particular time. A snapshot cannot be renamed or modified in any way., or reference trees A directory tree in users’ disk storage that instantiates a particular dynamic stream or snapshot. It contains a copy of the current version of each element in the stream or snapshot. A reference tree based on a dynamic stream can be updated, to incorporate the stream's recent changes.), AccuRev keeps track of the elements that are currently under active An element is said to be active in a workspace or stream if a new version of the element has been created there, and that version has not been either (1) promoted to the parent stream or (2) purged from the workspace or stream. See default group, backed, passive. An issue record is said to be active in a workspace or stream if the head version of one or more of its change package entries is in the stream's default group. development in that context. This set of elements is called the default group of the stream or workspace. [note ]
Workspace
The default group is a property of the workspace stream The private stream that is built into a workspace. All new versions of elements are originally created in workspaces; AccuRev records these versions in workspace streams., maintained in the AccuRev repository. There are no "hidden files" or other administrative structures in the workspace tree The ordinary directory tree, located in the user's disk storage, in which the user performs development tasks and executes AccuRev commands. to keep track of which elements are active.
The following commands cause an element to become a member of the workspace's default group. Note that these commands can be executed only in a workspace, not in a stream.
Keep
Rename (or cut-and-paste)
Defunct
undefunct (CLI only)
Merge (ends by performing a Keep)
Revert (ends by performing a Keep)
Paste Link (CLI command: ln)
Send to Workspace / Anchor
Dynamic Stream
When a version is Promote'd to a dynamic stream, the element becomes a member of the stream's default group.
If an element is already in the default group of a workspace or stream when one of the commands listed above is executed, the element simply remains a member. [note ]
For both a workspace and a dynamic stream, the following commands remove an element from the default group:
Promote (to the immediate parent stream)
Revert to Backed
The element returns to a passive An element that is not active in a workspace or stream is said to be passive in that workspace or stream. Passive versions can be overwritten by an update operation. state in the workspace or stream. A stream returns to inheriting a version of the element from its parent stream; a workspace returns to acquiring versions of the element from the backing stream through the Update command.
Cross-promoting an element to a stream that is not the immediate parent stream does not remove the element from the default group of the "from" stream.
The Stream Browser can show the development activity An element is said to be active in a workspace or stream if a new version of the element has been created there, and that version has not been either (1) promoted to the parent stream or (2) purged from the workspace or stream. See default group, backed, passive. currently taking place in each stream or workspace. A control below the stream or workspace opens or closes a subwindow that displays the details of the development activity. The activity details can appear in several ways -- by element, by transaction, or by issue record.
For a dynamic stream, the by-element display is a listing of the stream's default group. For a workspace, this subwindow displays those members of the default group that would be found in a Pending search (see discussion below).
The File Browser's Default Group search displays all the members of the default group of a stream or workspace.
A workspace's set of active elements (that is, its default group) is not quite the same as the set of elements with pending (not yet promoted) changes. In practice, the sets will often be the same. But in theory, the sets are overlapping, but not identical:
The Default Group search can include elements that are not pending. These are elements that you've "checked out" with Send to Workspace or Anchor.
The Pending search can include elements that are not in the default group. This is the set of a "non-member" elements -- those that have been modified (and thus are pending), but are not in the default group.