For each updated item, it prints a line that starts with a character reporting the action taken.These characters have the following meaning: A character in the first column signifies an update to the actual file, whereas updates to the file's properties are shown in the second column. As with most subcommands, you can limit the scope of the update operation to a particular tree depth using the , the update operation will omit or reenlist individual working copy members by modifying their recorded ambient depth to the depth you specify (fetching information from the repository as necessary). The repository is on these lines to start the external merge tool to resolve the conflicts.When the update is complete, the progress dialog shows a summary of the number of items updated, added, removed, conflicted, etc. This summary information can be copied to the clipboard using .— Tortoise SVN 1.7 Release notes "This command may take a while, and for some users, it may be more practical to simply checkout a new working copy." I'm running the command don't knowing what to expect, after 2 seconds the console replies upgraded '.' : P If you have just upgraded to SVN 1.7 on your machine (like I just did), and have a lot of projects in your Eclipse workspace which need to be upgraded, you can do the following in a terminal window on Unix-baesd systems: After Googling a bit, I found what seems to be the equivalent for Windows users: the answer by Alexey Shcherbak halfway down the page.If you're getting this error from Netbeans (7.2 ) then it means that your separately installed version of Subversion is higher than the version in netbeans.The standard Update command has no options and just updates your working copy to the HEAD revision of the repository, which is the most common use case.
Changes done by others will be merged into your files, keeping any changes you may have done to the same files.
As new versions of Subversion are released, the format used for the working copy metadata changes to accomodate new features or fix bugs.
Older versions of Subversion would automatically upgrade working copies to the new format the first time the working copy was used by the new version of the software.
This allows you to update your working copy to a specific revision, not only to the most recent one.
Suppose your working copy is at revision 100, but you want it to reflect the state which it had in revision 50 - then simply update to revision 50. This opens a new dialog where you can check all items you want in your working copy and uncheck all the items you don't want.