Description - Mks.com

If you check in a revision using an already existing revision number, Source Integrity attempts to
add one to the revision number and check it in as that revision. If that revision already exists,
Source Integrity then chooses the next available branch number and creates a new branch.
For example, if you are checking in a new revision to an archive where the head revision is 1.7, the
following numbers are valid:
● 1.8 (greater than head revision)--if you check in a revision as 1.7, which already exists,
Source Integrity assigns it 1.8
● 1.10 (greater than head revision)
● 1.72 (none of the numbers between 7 and 72 may be used afterwards)
● 2.0
● 1.7.1.1 (if it starts a new branch)
● 1.7.0.1 (leading zero as the branch number)
The following numbers are invalid:
● 1.3 even if there was no revision 1.3 previously
● 1.08 (leading 0 in last portion)
● 02.1 is considered the same as 2.1 (leading zero in branch number)
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.
--[no|confirm]ignoreUnresolvedMerge
controls whether to ignore a previously unresolved merge. For more information on merging
revisions, see si merge and si mergebranch.
-L label
--label=label
identifies a label that is applied to the new revision. Note the following about using labels:
❍ Labels cannot contain colons(:), square brackets ([ ]), or leading spaces.
❍ Labels cannot have the same format as a valid revision number.
❍ Labels that include spaces must be enclosed by quotes.
❍ MKS recommends not using hyphens (-) in labels. Using hyphens may cause some
si commands to fail.
--author=name
specifies an author name.
--[no]branch
controls whether to force the creation of a branch revision.
60 of 457