Description - Mks.com

EDT, PST, or GMT+/-hours:minutes. For timestamp examples, see the :time:timestamp option.
Note: Updating a revision by timestamp makes the most recent revision at the specified timestamp the member revision.
:memberbranchtip
identifies the tip revision on the member revision branch.
:working
identifies the working revision.
:trunktip
identifies the tip revision on the trunk.
state:statename
identifies the state, for example, Beta. This option is useful when you want to select revisions in a project that are in a specific
state.
For each project member, Source Integrity searches from the member revision on the development path to the root of the
archive to find a revision that corresponds to the specified state. If the member revision is on a branch, Source Integrity starts
from the tip revision and searches to the root of the archive; other branches in the archive are not searched. If no revision on
the development path matches the specified state, the command fails, stating "Revision does not exist."
devpath: devpathname
identifies the development path. This keyword only operates on member commands.
build: revisionnumber
identifies the build revision number, which must be a valid project revision number or project label in which a given member is
contained. Must specify a registered project. This keyword only operates on member commands.
:rule
identifies a rule defined with the si setmemberrule command.
link:p=project[::d=devpath][::m=member][::recurse] [::b=buildrevnumber]
allows you to set the member revision to whatever is the member revision for the corresponding member in a specific external
project configuration (normal, variant, build). Links the project that the member belongs to (the target project) with the master
project where:
project is the master project
devpath is the development path for the master project
member is a member in the target project. If not provided, the project is searched for a member with the same backing archive.
If recurse is specified, the search is recursive throughout the subprojects. There must be exactly one backing archive for each
member.
A possible application is to update all members to the same revision, even if they don't have the same backing archive.
-S sandbox
--sandbox=sandbox
specifies the location of a sandbox. In some cases, the commands that take this option do something with the sandbox contents
themselves. In other cases, specifying the sandbox location is simply a way to locate, or "point to", the corresponding project file. This
option is mutually exclusive with -P project|--project =project.
Note:
Locations that include spaces must be enclosed by quotes.
--user=name
identifies the user to use for connecting to the Integrity Server.
Universal Options
The following universal options apply to all MKS Integrity Suite commands.
--[no]batch
controls batch mode. Batch mode forces the application to process commands without prompting for responses.
--cwd=directory
acts as if the command is executed in the specified directory. In particular, any files and members in the selection are treated as being
relative to that directory.
Suppose you are working in the c:\sandbox directory and you want to issue the check out command so that the implicit sandbox
selection will work in a subdirectory, rather than having to specify the complete path for subdirectory sandbox names. You could use
the --cwd option to do this, for example:
si co --cwd=./demoapp/controls demoappctrl.c
341 of 457