User Guide - Mks.com

Backfill
Option (GUI)
Back
Revisions Only
Backfill
Option (CLI)
Function
Using the Apply CP Command
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 reduces the
total number of changes you bring into the
variant; however, this option 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 skip Results in an error if any backfill revisions are
specified during the Apply CP operation.
Ask to Specify ask Displays the backfill list. To complete the
Apply CP operation, you must accept the
entire list. If you decline the list, the Apply CP
operation fails.
In the Apply CP operation, you must accept the entire backfill list or the
operation fails. If you do not want to accept the entire backfill list, you
must instead perform a Resync CP operation. The Resync CP command
allows you to merge around unwanted revisions in your sandbox. For
more information on resynchronizing change packages, see “Using the
Resync CP Command” on page 406.
The next example illustrates how Apply CP handles a more complex
change package—one that contains code modifications that are dependent
on a new file. In this example, main.c is revised to call a value defined in a
new file, main.h.
The developer working on the code has checked in all these changes and
associated both files with CP 22:1. Development work then continues to
include a further revision to main.c which is checked in at revision 1.3 and
associated with CP 23:1. The main project therefore contains main.c at
revision 1.3 and main.h at revision 1.1.
395