02.05.2013 Views

User Guide - MKS

User Guide - MKS

User Guide - MKS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Command Options<br />

Setting Preferences<br />

Resynchronize continued Merge Type specifies the action to be taken when merging revisions. Select one of the<br />

following options from the list:<br />

Confirm causes Source Integrity to confirm the action to be taken when merging<br />

upon resync.<br />

Cancel causes Source Integrity to cancel the operation.<br />

Automatic causes Source Integrity to perform an automatic merge. For more<br />

information on automatic merging, see “Step Two: Merge Branch” on page 313<br />

Manual (Launch Tool) causes Source Integrity to initiate the <strong>MKS</strong> Visual Merge<br />

tool.<br />

On Conflicts specifies the action to be taken when merge conflicts occur. Select one of<br />

the following options from the list:<br />

Confirm causes Source Integrity to confirm the action to be taken each time a<br />

conflict occurs.<br />

Cancel causes Source Integrity to cancel the operation when a conflict occurs.<br />

Mark For Later Merge causes Source Integrity to mark the files for merging at<br />

another time, allowing you to resolve the conflict first.<br />

Launch Tool causes Source Integrity to initiate the <strong>MKS</strong> Visual Merge tool.<br />

Highlight Output File causes Source Integrity to highlight conflicts in the<br />

resulting merged revision.<br />

Resynchronize Change<br />

Package<br />

Use Master causes Source Integrity to operate on the top-level sandbox. When the<br />

selected change package is associated with a member in a subsandbox, specifying<br />

Use Master causes the command to operate on the top-level sandbox for that<br />

subsandbox.<br />

Overwrite Working File if Changed overwrites the working file even if it has changed.<br />

Perform Merges prompts you for confirmation before performing a merge operation.<br />

Confirm Actions causes Source Integrity to confirm all operations with you before<br />

starting them.<br />

Verbose provides additional information to track the status of the command.<br />

Already in Project is Error causes Source Integrity to terminate the operation if the<br />

member being applied is already in the project. If this setting is negated (as in<br />

noAlreadyInProjectIsError), the information is displayed as a warning.<br />

Ignore Server in Change Package causes Source Integrity to perform the Resync CP<br />

operation even if the change package members reside on different servers.<br />

Span Projects applies the command to any member specified in the change package,<br />

even if this involves multiple projects. This option allows Source Integrity to search<br />

across local sandboxes for all entries in the selected change package(s).<br />

Ignore Cross-Branch Entries causes Source Integrity to use the most recent revision<br />

when it encounters two revisions of the same member on different branches.<br />

Restore Revision Timestamp sets the timestamp of the working file to the date and<br />

time of the last checked-in revision in the history. If this option is cleared, the working<br />

file’s timestamp is set to the current date and time. The time stamp is only changed if<br />

the working file is modified. If the resynchronize does not change the working file, its<br />

timestamp remains the same.<br />

57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!