Description - Mks.com

Options
This command takes the universal options available to all si commands, as well as some general
options. See the options reference page for descriptions.
--lineTerminator=[lf|crlf|native]
explicitly identifies the characters to use as the line terminator for this sandbox. lf is a line
feed character, crlf is the combination of the carriage return and line feed characters, and
native uses the default line terminator in the client operating system: crlf in Windows and lf
in UNIX.
Note:
When you create a sandbox Source Integrity remembers the setting of the line
terminator, and all checkouts (using si co) and resyncs (using si resync) in that
sandbox use the same line terminator setting. If you want to override the line
terminator on an individual member, you must use some utility such as the MKS
Toolkit flip command.
--[no]populate
controls whether to populate the sandbox with read-only working files for all members.
--[no]sparse
controls whether to create a sparse sandbox.
Creating a sparse sandbox with --sparse affects the way the sandbox behaves with the
si ci check in command and the si co check out command, as well as si resync. This
option creates a sandbox with no working files and defers the creation of sandbox
directories and subsandboxes until you need to work with them. A sparse sandbox does not
retain working files when a member is checked in and continues to function this way
throughout its use; however, once created, sandbox directories and subsandboxes remain
in the sandbox. Using si ci to check in a member to a sparse sandbox removes the
working file from the sandbox (unless you did a check in locked, using the -l option).
Similarly, using si resync on the sandbox by default removes the working files for those
members that are not locked by you, although you can override this with
si resync --populate in a sparse sandbox, which in effect causes the resync to behave
like it does in a normal, non-sparse sandbox.
--[no]openView
controls whether to open the sandbox view after this new sandbox is registered on the
client. If --noopenView is used, the sandbox view does not open.
--[no]shared
controls whether or not to make the sandbox shared. The default is not shared.
Configuring the sandbox to be shared makes it possible for other users to share its working
files. Other users must first import the sandbox to register it with their Source Integrity clients
(see si importsandbox). When a top-level sandbox is configured to be shared, all
88 of 457