Command 'Copy (Branch/Tag)'

 

Symbol: _svn_icon_copy.png

Function: This command opens the SVN Copy Branch/Tag dialog. There you can Branch or Tag a revision of your project. A specific revi­sion of your project is saved there at this position. A branch is normally used in order to save changes isolated in one version. A tag is used for marking a specific state, for example a shipping version. Internally, it is copied not in the actual sense, but more refers to the revision.

Call: Menu bar: Project ‣ SVN .

Requirement: The project is versioned.

Dialog 'SVN Copy (Branch/Tag)'

SVN repository

From

SVN path of the current project

Example: https://svnserver/repository/trunk/ControlABC.project

To

Target path in the SVN repository for the copy operation

Example of tag: https://svnserver/repository/tags/V4.4.4.4/ControlABC.project

_cds_icon_input_assistent.png: Dialog SVN Repository Browser opens for selecting the target path.

Log message

Input field

Comment the change in a log message.

Example: Tag for version 4.4.4.4 created.

Recent Messages

Opens the dialog Recent Messages to display the last log messages. You can click a log message to accept it.

Create copy from

Working copy (including local changes)

The new branch/tag refers to the working copy including all local changes. The local changes are committed to the SVN repository for this purpose.

Base revision of working copy (<revision number>)

The new branch/tag refers to the base revision of your working copy whose revision number is displayed in the parentheses. If the working copy already contains local changes, then these are not committed to the SVN repository.

HEAD revision of the repository

The new branch/tag refers to the HEAD revision of your project.

Specific revision in SVN repository

_svn_img_revision_number.png 

The new branch/tag refers to a revision that is displayed on the adjacent button.

Click the button to change the revision. The dialog opens..

Switch to new location

_cds_icon_option_activated.png: After the dialog is confirmed, the working copy switches to the new branch/tag.

OK

The target path is created (as a new tag ../repository/tags/V4.4.4.4 or as a new branch ../repository/branches/new_feature). Then the revision specified in Create copy from is copied there.

See also