Some states in the Subclipse

U:working file was updated

G:changes on the repo were automatically merged into the working copy

M:working Copy is modified

C:this file conflicts with the version in the repo

?: This file was not under version control

!: This file is under version control and is missing or incomplete

A:This file'll is added to version control (after commit)

A +: This file is being moved (after commit)

D:this file'll be deleted (after commit)

S:this signifies that the file or directory have been switched from the path of the rest of the working copy (using SVN SW Itch) to a branch

I:ignored

X:external definition

~: Type Changed

R:item have been replaced in your working copy. This means the file is scheduled for deletion, and then a new file with the same name is scheduled for addition in its p Lace.

L:item is locked

E:item existed, as it would has been created, by an SVN update.

-A file ignored by version control. Can control what resources would be ignored by going towindow→preferences→team→ignored Resources.
-A file not under version control. These is typically new files, and the committed to the repository yet.
-A versioned file, needs to being added to the remote repository. These is typically files you had either renamed, or moved to a different directory.
-A Deleted folder. These is folders that and you had deleted locally without yet committing the changes to the repository. Note that files is usually removed from the view if they ' re deleted locally, so they is normally not seen with this IC On.
-A file with no local changes.
-A file with local, uncommitted changes.
-A locked file.
-A file that is needs a lock to being edited. These is typically files that cannot easily is merged (i.e. binary files), but could have many editors. A file needs a lock when itssvn:needs-lockproperty is set, and Subversion would attempt to make these files read-only in the file system to enforce proper lock negot ation.
-A conflicted file. These is typically files that had a commit/update conflict so you marked to resolve later.
-A file that has A tree conflict. These is typically files that has local changes, but has since been moved, removed, or renamed in the repository since The last local copy update.
-A file that's external to the project. Linked external files cannot is committed to the repository.
-A file that has been switched. These is files which belongs to a different working copy than their local parent directory.

in a synchronization view (e.g. via  Synchronize with Repository  or  Commit ), as Previously described, there was icons which indicate which direction a change is occurring in as well as additional inform ation about the change. These is described below:

outgoing
 -A file whose contents have been modified and would be committed to the REPOSITORY.
 -A file that'll be newly added to the repository. This could coincide with a file removal in cases where a file is moved or renamed.
 -A file that is removed from the repository. This could coincide with a file addition in cases where a file is moved or renamed.
 -A file with property changes, in the Commit dialog. On the Synchronize tab, property changes is currently reflected as a normal file modification ().

Incoming
 -A file that have content changes committed to the repository that'll be applied to The local copy.
 -A New file that is added to the local copy from the repository. Like the outgoing file addition, this could be the result of a move or rename.
 -A file that would be removed from the local copy because it had been removed from the repository. Like the outgoing file removal, this could be the result of a move or rename.

Conflict
 -A file that have been changed in both the local copy and repository independently, CA Using a need for conflict resolution. Fixing this condition involves opening up the conflict view or forcibly overwriting changes locally or remotely.
 -A file that has a tree conflict. This can occur when there be new changes to a file on one end (either local or remote), and the file is moved, removed, O R renamed on the other.

finally, the  Synchronize with Repository  option opens the Synchronize tab () with the following button S:

-Synchronizes the local copy with the currently selected repository when clicked. Selecting from the Drop-down allows switching between different remote code bases.
-Shows only incoming changes (remote→local).
-Shows only outgoing changes (local→remote).
-Shows both incoming and outgoing changes (remote local).
-Shows conflicting changes.
-Updates all local resources with incoming changes after prompt.
-Brings up the commit dialog to commit all outgoing changes.
-Breaks up the change lists by revisions.

Some states in the Subclipse