Description - Mks.com

controls whether to delay the checkin operation in the project until the deferred operation is
submitted. The operation in the sandbox still takes place immediately.
If reviews are mandatory, specify this option to submit the changes for review as a change
package. If this option is not specified, a pending revision is created for the operation, that
corresponds to a pending entry in the change package.
--descriptionFile=file
specifies a file name, file, containing the description text for the new revision. This option
and the -d or --description options are mutually exclusive.
-l
--[no]lock
controls whether to keep locks on members.
--[no|confirm]moveLabel
controls whether the application should move a label from one revision to another.
--nomoveLabel disables the moving of a label.
--confirmmoveLabel displays a confirmation message.
--moveLabel moves the label.
--[no]retainWorkingFile
controls whether to keep the working file in the sandbox after checkin. By default, a sparse
sandbox does not retain the working file after checkin.
--[no]saveTimestamp
controls whether to set the revision timestamp to the modification date and time of the
working file rather than the current date and time.
-u
--unlock
unlocks the newly checked-in revision. This is equivalent to specifying --nolock.
--[no]unexpand
controls whether to expand, unexpand, or ignore keywords in the member file. Keyword
expansion is only available in text archives, not binary archives. For descriptions of the MKS
Source Integrity keywords, see the Source Integrity Enterprise User Guide. Possible
keywords are:
$Author$
$CompanyInfo$
$Date$
$Header$
$Id$
$Locker$
$Log$
$Name$
63 of 457