Remote State (Pro Only)

Beside the local state all files also can have an assigned remote state. In contrast to the local state, the remote state is determined by repository content and hence needs a connection to the repository to be refreshed. It shows what will happen when performing a (recursive) Update command, e.g. 'Will be updated' or 'Will be removed'.

Use the Refresh Remote State command to manually refresh the remote state. Alternatively, it also can be optionally refreshed after executing some commands, e.g. after the Update command.

Following remote state values exist:

Unchanged you have the latest revision locally
Non-CVS there is no corresponding revision available in the repository yet (when adding files)
Needs Update there is a newer revision available in the repository; you will not be able to commit your changes for this file; use the Update command to get the changes from the repository
Needs Update (Conflict) there is a (newer) revision available in the repository, but you either have marked a new file for adding or an existing for removal
Will be Removed there is a newer, but removed revision in the repository; you will not be able to commit your changes for this file; using the Update command will delete this file locally or will produce a conflict (if the file is modified locally)
Sticky the file has a sticky tag or date and will not be changed by an Update command
Needs Refresh the remote state needs to be refreshed, it is out-of-date

Tip

To keep your remote state in sync with the repository, you can configure the refresh-options in Edit|Preferences.