02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

MKS cannot guarantee that the merged results are “correct”. MKS re<strong>com</strong>mends that you examine and<br />

test the merged results before checking them into the repository.<br />

--mergeType=manual <strong>com</strong>pletes the merge operation through the MKS Visual Merge tool. The MKS<br />

Visual Merge tool launches, displaying the revisions you want to merge. For more information on the<br />

MKS Visual Merge tool, refer to the Source Integrity Enterprise User Guide.<br />

--onMergeConflict =[confirm|cancel|mark|launchtool|highlight|error]<br />

specifies what to do when conflicts occur during a merge.<br />

--onMergeConflict=confirm prompts you to confirm a merge conflict option.<br />

--onMergeConflict=cancel cancels the merge.<br />

--onMergeConflict=mark marks the revisions indicating that merging is required without<br />

<strong>com</strong>pleting all of the merge related tasks. This provides time you may need to investigate conflicts or<br />

consult on editing or difference blocks before finishing the merge.<br />

--onMergeConflict=launchtool launches the MKS Visual Merge tool to resolve the conflicts, all nonconflicting<br />

blocks will already have been applied.<br />

--onMergeConflict=highlight indicates conflicts in the file with the following characters: "".<br />

--onMergeConflict=error indicates merge conflicts with an error message prompt.<br />

Note: --onMergeConflict=launchtool does not require the -g or --gui options.<br />

--[no]branch<br />

controls whether to force the creation of a branch revision. Specifying --branch always creates a<br />

branch.<br />

For details on branch revisions, see the si ci reference page.<br />

--[no|confirm]branchVariant<br />

controls whether Source Integrity should create a branch off of the revision you are checking out, if you<br />

are working in a variant sandbox. This reduces the possibility of locking conflicts with the member while<br />

work is being done in the variant and regular sandboxes. Specifying --confirmbranchVariant<br />

causes a prompt to be displayed so you can confirm the branching.<br />

This option overrides the branchIfVariant preference that you can set with the si setprefs<br />

<strong>com</strong>mand.<br />

This option is useful because development paths can conflict when developers working on different<br />

paths need to work on the same revision of a file. There is also the potential to conflict when<br />

development paths access the same member histories. For example, suppose the current version of a<br />

project includes utility.dll, version 1.4 and the variant sandbox contains utility.dll, version<br />

1.3. Both versions are stored in the same member history, and therefore a conflict is possible. Using<br />

the --branchVariant option helps handle such conflicts.<br />

68 of 457

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

Saved successfully!

Ooh no, something went wrong!