Description - Mks.com

can also be used to resolve merge conflicts.
Because a propagation change package records all the changes that need to be propagated
between development paths, it is useful when incremental and repeated use of the Resync CP
command is used to collect project changes.
What is a Propagation Change Package?
Technically, a propagation change package is a normal change package used to propagate
specific changes from one development path to another. Conceptually, a propagation change
package is a change package used to record and resolve changes that need to be applied
between development paths. Similar to a resolution change package, a propagation change
package records the changes that need to be made to resolve a merge. Unlike a resolution change
package, a propagation change package records member changes and can be used across other
development paths like a normal change package after it has been submitted.
When Should I Use a Propagation Change Package?
You need to use a propagation change package if an Apply CP operation includes undesirable
member changes. You can use the Resync CP command to populate the propagation change
package with the undesirable member changes in the form of deferred member operations. The
undesirable member changes can then be discarded from the propagation change package prior to
submission.
Rather than perform one large Apply CP or Resync CP operation that can take a long time, a
propagation change package allows you to incrementally propagate changes between
development paths. Once the propagation change package is submitted, it records the changes
made to the project.
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.
--allowOpenCP
allows Source Integrity to apply open change packages.
--[no]alreadyInProjectIsError
Causes Source Integrity to terminate the operation if the member being resynchronized is
the same one listed in the change package and is already in the project. If this setting is
negated --noalreadyInProjectIsError, then the information is displayed as a
warning.
--backFill=[cp|revision|error|skip|ask]
Specifies the way Source Integrity treats historic revisions required by the specified change
package. For example, --backfill=ask means Source Integrity asks you to specify the
change packages you want to exclude from the operation.
211 of 457