User Guide - MKS

Resync CP
Advanced Command Options
Function
Verbose Provides additional information to track the status of the command.
Using the Resync CP Command
Already in Project is Error Causes Source Integrity to terminate the operation if the member being applied is
already in the project.
If this setting is negated, then the information is displayed as a warning.
Ignore Server in Change
Package
Causes Source Integrity to perform the Resync CP operation even if the change
package members reside on different servers.
Span Projects Applies the command to any project specified in the change package, even if this
involves a project that is not the one you initially targeted.
In a Resync CP operation, this option allows Source Integrity to search across
local sandboxes for all the entries contained in the selected change package(s).
Ignore Cross-Branch Entries Causes Source Integrity to use the most recent revision when it encounters two
revisions of the same member on different branches.
Restore Revision Timestamp Sets the timestamp of the working file to the date and time of the revision in the
history. If this option is not set, the working file’s timestamp is set to the current
date and time.
Other Project is Error Terminates the command if the member is not in the project you are applying to,
or in its variant.
Allow Open Change Packages Allows Source Integrity to work with open change packages. This facilitates the
application of a resolution change package.
Create Variants Causes Source Integrity to create new variant subprojects within the variant
project as required to apply the change package members. If the main project
contains required files that reside in a subproject, the Create Variants option
creates variant subprojects for these files to be placed into.
Merge On Branch Causes Source Integrity to perform a merge if the target revision is on a branch.
Source Integrity differences the two file revisions and merges any changes into
the working file without modifying its revision number. You must then check in the
working file to advance the revision to the next available revision number.
393