The co (“check out”) command adds elements to your workspace’s
default group, the collection of elements that are under active development in that workspace. With the
-v or
-t option, it also overwrites the file in your workspace with an old version of the element. Be careful when using these options:
An important effect of the co command is to “shield” the specified elements from being changed by an
update command.
update always skips over the members of the default group when deciding which elements to update.
To remove an element from the workspace’s default group, use the purge command. This also overwrites the file in your workspace with the version in the backing stream.
The -v and
-t options cause an old version of the element to be copied into your workspace. By default, each file copied into your workspace by this command has its timestamp set to the current time. If environment variable
ACCUREV_USE_MOD_TIME is set, the timestamp is set to the time the version was originally created. (Note: that’s the time the version was created in some user’s workspace stream, not the time it was subsequently promoted to the backing stream.)
When used with the -n option, overrides timestamp optimization. When
-O is used,
all files are considered, even those whose modification times have
not changed since the last time the workspace was updated or searched for modified files. Having to check all files, regardless of modification time, slows
co performance. In anchor-required workspaces, overrides the warning message encountered when operating on an element that is active in a sibling workspace.
Get and checkout the version of file foo.c that is currently used by stream
gizmo_bugfix: