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.

si mergebranch<br />

merges a branch revision into a single revision<br />

SYNOPSIS<br />

si mergebranch [--[no|confirm]branch] [--[no|confirm]branchVariant]<br />

[--mergeType=[confirm|cancel|automatic|manual]]<br />

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

[--branchRevision=value] [(--cpid ID|--changePackageId=ID)] [--issueId=ID]<br />

[(--[no]lock)] [--targetRevision=value] [(-R|--[no|confirm]recurse)]<br />

[--filter=filteroptions] [(-S sandbox|--sandbox=sandbox)] [--hostname=server]<br />

[--port=number] [--password=password] [--user=name] [(-?|--usage)]<br />

[(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory]<br />

[--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]]<br />

[--status=[none|gui|default]] sandbox member...<br />

DESCRIPTION<br />

si mergebranch allows you to <strong>com</strong>bine the development occurring on different branches by<br />

merging the branched revisions into a single revision.<br />

Source Integrity recognizes cases where a previous merge has occurred, (whether by merging the<br />

branch, automatic merging, or using the MKS Visual Merge and MKS Visual Difference tools), and<br />

merges only changes since the last merge operation. Thus, the first merge branch operation<br />

occurring on a given branch merges all changes throughout the branch. Any subsequent merge<br />

branch operations will merge only changes since the previous merge operation.<br />

Options<br />

This <strong>com</strong>mand takes the universal options available to all si <strong>com</strong>mands, as well as some general<br />

options. See the options reference page for descriptions.<br />

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

specifies whether to create a branch off of the target revision (the member revision that the<br />

working revision is merged into), if it is locked by another user.<br />

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

specifies whether to create a new branch for the merged revision, if the specified variant<br />

does not already have a branch.<br />

--mergeType=[confirm|cancel|automatic|manual]<br />

specifies how you want to <strong>com</strong>plete the merge.<br />

--mergeType=confirm prompts you to confirm a merge type.<br />

161 of 457

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

Saved successfully!

Ooh no, something went wrong!