15.2.2. Using source control commands

Click the Source control button drop-down arrow to access the source control commands. The options available from this menu depend on the status of the file loaded into the File Editor pane and the version control tool you are using.

Locked, read-only files

If you are working with a locked file, click the Source control button drop-down arrow to display the Source control menu shown in Figure 15.1.

Figure 15.1. Source control menu for locked files

Source control menu for locked files

The menu options are:

<Not Editable>

Indicates the status of the file as Locked and so it cannot be edited.

Raise WinCVS

Starts up the version control tool.

Prompt before Submitting

Source control commands chosen from the Source control menu are submitted directly for execution. Click this option to display a prompt showing the command before submission, see Setting up a prompt for details.

If you are working with a read-only file, the Source control menu includes:

Allow Editing

Click to change the status of the file to Read-Write so that it can be edited.

RealView Debugger warns if the contents of the buffer have changed since the file was last saved.

Read-Write files

If you are working with an editable file, click the Source control button drop-down arrow to display the Source control menu shown in Figure 15.2.

Figure 15.2. Source control menu for read-write files

Source control menu for read-write files

In this example, the menu options include:

Make Buffer Read-Only

Changes the status of the file to Read-only so that it cannot be edited.

Check-In File

Checks the current file into the repository. Selecting this option displays a message dialog box where you can enter a text comment, for example Updated for new tools env. This is used as the message to identify the check-in, for example:

cvs commit -m “Updated for new tools env” filename

UnCheck-Out File

Updates the current file to synchronize it with any changes saved to the repository since it was last checked out or committed, for example:

cvs update filename

The original file is renamed, for example dhry_1.c.old.

Enter File into Source Control

Adds the current file to the repository, for example:

cvs add filename

Raise WinCVS

Starts up the version control tool.

Show Files You have Checked Out

Updates the current file to merge changes. Where a file contains changes, this is roughly equivalent to a checkout command, for example:

cvs -nq update

This does not complete the update, defined by the -n flag. It is also quiet (-q flag).

Show Version History

Displays the history information for the current file, for example:

cvs -q log -N filename

This does not list tags, defined by the -N flag. It is also quiet (-q flag).

Show Changes from Previous Version

Displays differences between the current file and the previous version in the repository, for example:

cvs diff filename

Show Differences of two Versions

Displays differences between two versions of the file currently checked out. Selecting this option displays the first of two prompts where you specify the version numbers to compare, for example:

cvs diff -r 1.1 -r 1.3 filename

Show Tags

Displays status information for the current file, including tags, for example:

cvs status -v filename

File Status

Displays status information for the current file, for example:

cvs status filename

Merge Changes

Updates the current file to merge changes. Where a file contains changes this is equivalent to a checkout command, for example:

cvs update filename

This does complete the update.

If you are working with a custom version control tool, that is one that is not supported by RealView Debugger by default, you can specify the commands submitted. These appear as options on the menus described in this section. See Specifying custom commands for details on setting up these custom commands.

Copyright © 2003, 2004 ARM Limited. All rights reserved.ARM DUI 0234B
Non-Confidential