CLI User's Guide - AccuRev

(remove command), its versions become inaccessible. This is not irrevocable, though: you can
reactivate a stream, making its versions accessible again, with the reactivate command.
Getting Work Done with the CLI
AccuRev does not force you to proceed with your software development work in any particular
way. The workflow described in the following sections shows how you can put the AccuRev CLI
to good use, but it certainly isn’t the only way to get your work done.
Our example workflow includes these topics:
• Creating a Workspace
• Placing Files Under Version Control
• Editing Files in a Workspace
• Checkpointing — Saving Private Versions
• Comparing Versions of a Text File
• Making Your Changes Public
• Concurrent Development — Working Well with Others
• Determining the Status of Files
• Getting in Touch With Your Past
• Tracking Other Users’ Work
• Incorporating Other Users’ Work into Your Workspace
• Concurrent Development — When Streams Collide
Creating a Workspace
Use the accurev mkws command to create a new workspace. Using command-line options, you
must specify three parameters:
• Name of backing stream (–b option): Each workspace is associated with (or “based on”, or
“backed by”) one of the depot’s streams. If a depot represents a particular development
project, then a stream represents a sub-project. The backing stream acts as a “data
switchboard”, organizing the sharing of your changes to files with changes made by other
members of your development team.
You can name any dynamic stream or snapshot (static stream) as the backing stream for the
new workspace. You cannot choose a workspace stream — a workspace cannot be based on
another workspace. For example, to specify the stream named brass_dvt as the backing
stream:
-b brass_dvt
• Name of new workspace (–w option): AccuRev identifies each workspace by a simple name,
which must be unique across the entire repository. That is, two workspaces cannot have the
AccuRev® CLI User’s Guide 19