AccuRev CLI User's Guide

In a sparse workspace, this status also applies to elements that are not currently loaded into the
workspace. The ability to create a new sparse workspace was disabled in AccuRev Version
3.5; use the Include/Exclude facility in a new workspace instead. See the incl, excl, and
incldo reference pages.
• (twin) — the element is one of multiple elements in the workspace that exist at the same
pathname. At most one of these elements can be accessed through the pathname; the other(s)
can be accessed through their unique element-IDs. See Version Control of Namespace-
Related Changes on page 65 in AccuRev Technical Notes.
• (stranded) — the element is active in the workspace, but cannot be accessed through the file
system. This can occur in several situations:
• There is no pathname to the element, because the element’s directory (or a higher-level
directory) was removed from the workspace or stream.
• (dynamic stream only) There are one or more defunct elements at a given pathname, along
with one non-defunct element. The defunct element(s) have (stranded) status.
• The element’s directory (or a higher-level directory) is cross-linked, making another
version appear at the pathname of the active version.
Changes to the element in the workspace:
• (modified) — the file has been modified in the workspace since the most recent update or
keep. See Optimized Search for Modified Files — the Scan Threshold on page 218.
• (kept) — a new version of the element has been created with keep, move, defunct, or
undefunct, and the file has not subsequently been modified, promote’d to the backing
stream, or purge’d.
• (member) — the element is “active” in the workspace (is in the workspace stream’s default
group). The commands that create a new version, listed above, also make the element active.
So do the commands anchor, co, and revert.
Relationship to the version in the backing stream:
• (backed) — the version in the workspace stream is the same as the version in the backing
stream. And you have not changed the element since the last time you promote’d or purge’d
it, or since the most recent update of your workspace.
• (stale) — the element needs to be updated, because the version in the backing stream has
changed since the workspace’s latest update. And since you have not changed the element in
your workspace, it can be safely updated.
• (overlap) — the element has changed both in the backing stream and in your workspace. This
indicates that a merge is required before you can promote your changes to the backing stream.
Prior to AccuRev 4.6, “underlap” files were considered to have “overlap” status.
• (underlap) — similar to overlap: the element has changed both in the backing stream and in
your workspace, but the changes in your workspace have already been promoted to the
backing stream. (More precisely, your version is an ancestor of the backing stream’s version.)
In many cases, no promote is required; you can just purge the changes from your workspace,
AccuRev CLI User’s Guide 10