The Working Copy view allows you to manage the content of an SVN
The toolbar contains:
- the list of defined working copies
- a set of view modes that allow you to filter the content of the working copy based on
the resource status (like incoming or outgoing changes)
- Settings menu
If you click any of the view modes (All Files
), the information
displayed changes as follows:
Working Copy View - Modified View Mode
- Incoming -
The resource tree presents only incoming changes.
- Outgoing -
The resource tree presents only outgoing changes.
- Conflicts -
The resource tree presents only conflicting changes (real conflicts, pseudo-conflicts, and
files in the Name
The following columns provide information about the resources:
- Name - Resource name. Resource icons can have the
following decorator icons:
- Local file status -
Shows the changes of working copy resources that were not committed to the repository yet.
The following icons are used to mark resource status:
- - Resource is not under
version control (unversioned).
- - Resource is being ignored
because it is not under version control and its name matches a file name pattern
defined in one of the following places:
- - Marks a newly created resource,
scheduled for addition to the version control system.
- - Marks a resource
scheduled for addition, created by copying a resource already under
version control and inheriting all its SVN history.
- - The content of the resource has been
- - Resource has been replaced
in your working copy (the file was scheduled for deletion, and then a new file with
the same name was scheduled for addition in its place).
- - Resource is
deleted(scheduled for deletion from Repository
upon the next commit).
- - The resource is
incomplete (as a result of an interrupted check out or
- - The resource is missing
because it was moved or deleted without using an SVN-aware application.
- - The contents of the resource is in
- - Resource is in tree
conflict state after an update operation because:
- Resource was locally modified and incoming deleted from repository;
- Resource was locally scheduled for deletion and incoming modified.
- - Resource is obstructed
(versioned as one kind of object: file, directory, or symbolic link, but has been
replaced outside Syncro SVN Client
by a different kind of object).
- - Resource is in name conflict state (only on
case insensitive systems like Windows). This happens when two files having the same
name (ignoring letter-cases) exist in the same repository folder (for example
file.txt and File.txt). The two files were
added to repository from a case-sensitive operating system like Linux or Mac OS X.
This state is reported after an update operation and most of the Apache SubversionTM operations
cannot be performed over such files. The solution is to rename one of the files from a
case-sensitive operating system or directly from the
Repositories view in order to have the files with completely
properties status - Marks the resources that have SVN
properties, with the following possible states:
- - The resource has SVN
- - The resource
properties have been modified.
- - Properties for this
resource are in real conflict with property updates received
from the repository.
- Revision - The current revision number of the
- Date - Date when the resource was last time modified on
- BASE Revision - The revision number of the pristine
version of the resource.
- BASE Date - Date when the pristine version of the
resource was last time committed in the repository.
- Author - Name of the person who made the last
modification on the pristine version of the resource.
file status - Shows changes of resources recently modified in
the repository. The following icons are used to mark incoming resource status:
- - Resource is newly
added in repository.
- - The content of the
resource has been modified in repository.
- - Resource was
replaced in repository.
- - Resource was deleted
Remote properties status - Resources marked with the icon have incoming modified
properties from the repository.
- Remote revision - Revision number of the resource latest
- Remote date - Date of the resource latest modification
committed on the repository.
- Remote author - Name of the author who committed the
latest modification on the repository.
- Lock information - Shows the lock state of a
resource. The lock mechanism is a convention intended to help you signal other users that
you are working with a particular set of files. It minimizes the time and effort wasted in
solving possible conflicts generated by clashing commits. A lock gives you exclusive
rights over a file, only if other users follow this convention and they do not try to
bypass the lock state of a file.
A folder can be locked only by the SVN client
application, completely transparent to the user, if an operation in progress was
interrupted unexpectedly. As a result, folders affected by the operation are marked with
the symbol. To clear
the locked state of a folder, use the Clean up action.
The following lock states are displayed:
Note: Users can lock only files.
- no lock - the file is not locked. This is the default state of a file in the
- remotely locked () - shown when:
If you try to commit a new revision of the file to the repository, the server
does not allow you to bypass the file lock.
- another user has locked the file in the repository;
- the file was locked by the same user from another working copy;
- the file was locked from the Repositories view.
Note: To commit a new revision, you need to wait for the file to be unlocked.
Ultimately, you might try to break or steal the lock, but this is
not what other users expect. Use these actions carefully, especially when you are
not the file lock owner.
- locked () -
displayed after you have locked a file from the current working copy. Now you have
exclusive rights over the corresponding file, being the only one who can commit
changes to the file in the repository.
Note: Working copies keep track of their locked
files, so the locks are presented between different sessions of the application.
Synchronize your working copy with the repository to make sure that the locks are
still valid (not stolen or broken).
- stolen () - a
file already locked from your working copy is being locked by another user. Now the
owner of the file lock is the user who stole the lock from you.
- broken () - a
file already locked from your working copy is no longer locked in the repository (it
was unlocked by another user).
Note: To remove the stolen or broken
states from your working copy files, you have to Update
If one of your working copy files is locked, hover the mouse pointer over the lock
icon to see more information:
- lock type - current file lock state;
- owner - the name of the user who created the lock;
- date - the date when the user locked the file;
- expires on - date when the lock expires. Lock expiry policy is set in the
repository options, on the server side;
- comment - the message attached when the file was locked.
- Size - Resource size on disk;
- Type - Contains the resource type or file extension.
Note: The working copy table allows you to show or hide any of its columns and also to
sort its contents by any of the displayed columns. The table header provides a
contextual menu which allows you to customize the displayed information.
The toolbar allows you to switch between two working copies: