AccuRev CLI User's Guide

Selecting Non-Member Modified Elements
If you want to make the best use of the default group, you will periodically need to add modified
elements to the default group if they aren’t already in it. You can select non-member modified
elements with the –n option. To add all non-member modified elements to the default group:
accurev co -n
Selecting Pending Elements
The end goal of any change is to promote that change to the backing stream. All changes, whether
kept or not, are considered to be pending. Pending is short for “pending promotion”. The pending
option is necessary because –k does not select modified elements and –m does not select kept
elements. To list all elements that are pending promotion in the current workspace:
accurev stat -p
Selecting Overlapping/Underlapping Elements
Elements that you have changed and have also been changed in the backing stream since you last
updated your workspace are called overlapping. Before you can promote these elements, you
must merge your changes with the new changes in the backing stream. To get a list of all
overlapping elements:
accurev stat -o
When you are ready to do the merges, you can do a merge of all overlapping elements very
simply:
accurev merge -o
Underlap status is similar to overlap status, in that an element has changed in your workspace and
also in the backing stream. With underlap, the changes in your workspace version have already
been promoted to the backing stream (from another workspace, or from a stream elsewhere in the
depot’s stream hierarchy). In many cases, the most appropriate action is to use the purge
command to “undo” the changes in your workspace. In other cases, a merge-promote sequence is
most appropriate.
To get a list of all underlapping elements:
accurev stat -U
To purge the changes in underlapping elements, specify them on the command line or in a listfile:
accurev purge blink.java BlinkProj.doc
Note: purge restores the version of an element that was in the backing stream at the time of your
workspace’s most recent update. You might need to perform another update to bring the version
causing the underlap status into the workspace.
AccuRev CLI User’s Guide 14