CLI User's Guide - AccuRev

• (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 237.
• (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 merge and revert, which invoke the keep command. And so do the
commands anchor and co, which make an element active by creating a virtual version in the
workspace.
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,
restoring the version that was in the backing stream at the time of the workspace’s most recent
update. Prior to AccuRev 4.6, “underlap” files were considered to have “overlap” status.
In a new workspace, the status of every element is backed. This means that the version in your
workspace is identical to the version in the backing stream. The following sections describe the
other statuses.
AccuRev® CLI User’s Guide 11