Working Copy View

Modified

• - incoming modification from repository:
  • - file content or properties modified remotely
  • - new file added remotely
  • - file deleted remotely
• - outgoing modification to repository:
  • - file content or properties modified locally
  • - new file added locally
  • - file deleted locally
• - pseudo-conflict state - a resource being locally and remotely modified at the same time, or a parent directory of such a resource.
• - real conflict state - a resource that had both incoming and outgoing changes and not all the differences could be merged automatically through the update operation (manually editing the local file is necessary for resolving the conflict).

• Additional status information:

  • Propagated modification marker - A folder marked with this icon indicates that the folder itself presents some changes (like modified properties) or a child resource has been modified.

  • External - This indicates a mapping of a local directory to the URL of a versioned resource. It is declared with a svn:externals property in the parent folder and it indicates a working copy not directly related with the parent working copy that defines it.

  • Switched - This indicates a resource that has been switched from the initial repository location to a new location within the same repository. The resource goes to this state as a result of the Switch action executed from the contextual menu of the Working Copy view.

  • Grayed - A resource with a grayed icon but no overlaid icon is an ignored resource. It is obtained with the Add to svn:ignore action.

• Current SVN depth of a folder:

  • Immediate children (immediates) (a variant of sparse checkout) - The directory contains only direct file and folder children. Child folders ignore their content.

  • File children only (files) (a variant of sparse checkout) - The directory contains only direct file children, disregarding any child folders.

  • This folder only (empty) (a variant of sparse checkout) - The directory discards any child resource.

  Note:

  • Any folder not marked with one of the depth icons, has recursive depth (infinity) set by default (presents all levels of child resources).
  • Although folders not under version control can have no depth set, Syncro SVN Client presents unversioned and ignored folders with empty depth when Show unversioned directories content or Show ignored directories content options are disabled.

Local file 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:
  • global-ignores section in the SVN client-side config file.
    Attention: If you don't explicitly set the global-ignores runtime configuration option - either to your preferred set of patterns or to an empty string - Subversion uses the default value.
  • Application global ignores option of Syncro SVN Client.
  • the value of a svn:ignore property set on the parent folder of the resource being ignored.
• - 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 modified.
• - 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 update operation).
• - The resource is missing because it was moved or deleted without using an SVN-aware application.
• - The contents of the resource is in real conflict state.
• - 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).

Local properties status

• - The resource has SVN properties set.
• - The resource properties have been modified.
• - Properties for this resource are in real conflict with property updates received from the repository.

Remote file 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 from repository.

Lock information

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.

• no lock - the file is not locked. This is the default state of a file in the SVN repository.
• remotely locked () - shown when:
  • 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.
  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.
  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 them.