User Guide - Mks.com

Working on a
Variant
Resync CP Backfill Options
Backfill
Option (GUI)
Entire
Change
Packages
Back
Revisions
Only
Backfill
Option (CLI)
Function
Using the Resync CP Command
cp Selected by default for the Resync CP
command. Recursively finds all historic
revisions required by the specified change
packages and applies them. It does not ask
you to confirm the backfill list.
revision Processes only the changes in the specified
change package(s). Any change packages
associated with intermediate revisions are not
picked up.
Note: Processing by revision may result in
broken builds because indirectly associated
files are not picked up.
Error error Results in an error if other change packages
are required but not specified.
Skip
Revisions
Ask to
Specify
skip Causes Source Integrity to merge around
specified backfill revisions.
ask Displays the backfill list and asks you to
specify how you want Source Integrity to treat
the change packages.
Working on a variant allows you to create a specific change, test it, and
then bring that change back into the main trunk of development. Within
reason, this can be done even when the main trunk includes further new
development.
For example, a patch created in a variant project is needed in the master
project. The file—utility.c—has a head revision of 1.4 in the project. In
the variant project, the file utility.c version 1.2 is checked out to
revision 1.2.1.1 and the code is revised. The file utility.c is then checked
in at 1.2.1.2 and associated with CP 5:1.
413