Tortoise svn common icon meaning and icon can not be resolved properly!

It programmer development Essentials-all kinds of resources download list, history of the most IT resources, personal collection summary.

Green tick : The icon indicates that this is a newly removed working copy, and his subversion status is normal.

Gray tick : The gray icon indicates "read Only" and if you set the Svn:needs-lock property to a file, subversion will make this file read-only until you get the file lock. A read-only file has this overloaded icon to indicate that you must get a lock before editing.

Red exclamation point: When you start editing a file, the status of the file becomes modified, and the icon turns into a red circle with an exclamation point. This way you can easily know which files have been modified since the last update and which files need to be submitted.

Yellow exclamation point: A triangular sign with an exclamation point indicates a conflict (conflict) has been created in a single update.

Blue plus sign : This means that the file or folder has been scheduled to be added under version control.

Red Fork : Indicates that the file or folder is scheduled to be deleted (deleted), or that the file is missing.

Gray Line : Indicates that version control is not controlled and is ignored.

Blue question mark : not yet received version control, but not ignored.

Lock : Indicates that the file is locked, his subversion status is normal, the lock must be released before someone else's changes can be submitted.

The SVN icon does not display the problem resolution correctly:
1. Using the SVN plugin as a version controller in MyEclipse or eclipse has always been normal. But suddenly one day, the version number and the hint icon of files under Project are gone, and after checking svn is normal.
Start with the wrokspace. Metadata Delete, and then re-import project workspace under normal use.
But now a more convenient approach is found:
Go to: windows->preferences->general->appearance->labledecorations tick one of the SVN entries. Alternatively, you can open WINDOWS->PREFERENCES->TEAM->SVN to make the relevant settings.

2. Recently updated SVN software, after the update found that the Sync folder does not tick mark, the internet said to check the SVN settings:
Right-->tsvn-> Set-> Style-> Overlay icon->statuscache
There are three options:
1Default
2Shell
3None
If it is the first two, there should be an SVN icon, if none, there is no.
But can not solve the problem, and later with the installation file repair function to solve the problem, that is, double-click the installation file, select Repair, and then restart the system. This seems to be a common problem with the SVN update.

Project View the package Explorer view

-version-controlled files have been ignored. Files can be ignored by window→preferences→team→ignored Resources.
A file ignored by version control. You can control what resources would be a ignored by going to window→preferences→team→ignored resources.

-Files that are not included in the version control are generally new and have not yet been submitted.
A file not under version control. These is typically new files, and the committed to the repository yet.

-locally renamed or moved files to a different directory.
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.

-Locally deleted directories.
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.

-No changes to the file.
A file with no local changes.

-Files that have not been submitted have been changed.
A file with local, uncommitted changes.

-Files in a locked state.
A locked file.

-There is a conflict not resolved, just update or submit the file.
A conflicted file. These is typically files that had a commit/update conflict so you marked to resolve later.

-Files that have a directory tree conflict. Typically, files on the repository are moved, deleted, or renamed after the most recent update.
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.

-the file referencing the external project cannot be submitted to the resource library of this project.
A file that's external to the project. Linked external files cannot is committed to the repository.

-A file with a branched version. These files belong to a different working directory and not to the local parent directory.
A file that has been switched. These is files which belongs to a different working copy than their local parent directory.

move out of outgoing view

-Files that have changed locally.
A file whose contents has been modified and would be committed to the repository.

-locally added files.
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.

-Locally deleted files.
A file that would be removed from the repository. This could coincide with a file addition in cases where a file is moved or renamed.

-The local file attribute has changed the file.
A file with property changes, in the Commit dialog. On the Synchronize tab, property changes is currently reflected as a normal file modification ().

Moving into Incoming view

-Files that need to be updated.
A file that had content changes committed to the repository, that'll be applied to the local copy.

-Additional files that need to be moved in.
A new file that would be added to the local copy from the repository. Like the outgoing file addition, this could be the result of a move or rename.

-Files that were deleted in the repository.
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 Conflict View

-a repository and locally modified files at the same time.
A file is been changed in both the local copy and repository independently, causing a need for conflict resolution. Fixing this condition involves opening up the conflict view or forcibly overwriting changes locally or remotely.

-Files that have been renamed or moved or deleted on the remote repository.
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.

The "Synchronize with Repository" option opens some buttons on the interface Others:

Finally, the Synchronize with Repository option opens the Synchronize tab () with the following buttons:

-Synchronize selected files, drop-down arrows to switch between different remote directories.
Synchronizes the local copy with the currently selected repository when clicked. Selecting from the Drop-down allows switching between different remote code bases.

-only files that need to be moved are displayed.

Shows only incoming changes (remote→local).

-only files that need to be submitted are displayed.

Shows only outgoing changes (local→remote).

-also displays the need to update or submit files.

Shows both incoming and outgoing changes (remote↔local).

-only files that are conflicting are displayed.

Shows conflicting changes.

-Update all files.

Updates all local resources with incoming changes after prompt.

-Submit all documents.

Brings up the commit dialog to commit all outgoing changes.