问题
When I commit to SVN and after that update both via the shell extension of Tortoise SVN, the update sets me back to the revision before my commit.
I can verify this in two ways. First of all after my commit it says that after my commit I am at revision 22058 and after the update it tells my I am at revision 22057. When I call "Check for Modifications" and choose "Check Repository" there, it tells me that the HEAD-Revision is 22058.
Still an update yields "at revision 22057"
This even happens if I choose "Update to revision" and select "HEAD revision".
The only way to get the latest revision is deleting my entire working copy and checking it out again - but then the problem reoccurs when I commit again.
回答1:
Just for the record:
The problem was that TortoiseSVN was in offline mode. The solution was to open the log view for the workspace root and then pressing F5. Refreshing the log causes TortoiseSVN to switch back to online mode.
回答2:
Do you have a sparse checkout? Alternatively, you've checked out a subdirectory where the last commit is in your working copy even though the repo has other, later commits that are not part of your WC.
A Quick run through "Check for Modifications" using the "check repository" button shows this is working as intended. The commit revs for the list of modified files is what's listed in those 2 values.
At the bottom of the dialog you can see a summary of the range of repository revisions in use in your working copy. These are the commit revisions, not the update revisions; they represent the range of revisions where these files were last committed, not the revisions to which they have been updated. Note that the revision range shown applies only to the items displayed, not to the entire working copy. If you want to see that information for the whole working copy you must check the Show unmodified files checkbox.
来源：https://stackoverflow.com/questions/25542610/tortoise-svn-does-not-update-to-head-revision-correctly