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.can occasionally be useful to see what your project looked like at some earlier point in its history.But in general, updating individual files to an earlier revision is not a good idea as it leaves your working copy in an inconsistent state.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 .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.
If you want to undo changes to a file and start afresh from an earlier revision, you can rollback to a previous revision from the revision log dialog.
Take a look at the section called “Roll back (Undo) revisions in the repository” for further instructions, and alternative methods.
If the file you are updating has changed name, you may even find that the file just disappears from your working copy because no file of that name existed in the earlier revision.
You can also choose whether to ignore any external projects in the update (i.e.
projects referenced using error messages when you try to commit them!