ANSWER:

What Subversion is showing you is that you’ve checked out revision 584. The information is taken directly from the .svn/entries file, and not from the server.

This stems from Subversion’s basic design of not requesting information from the repository server whenever possible. It was a decision made to allow users to have a lot of Subversion’s power if they happen to be working remotely and have no network connection to the repository server.

• If you do a svn info on one of the files just committed, you’ll see that file is at revision 620.
• If you did a svn info http://www.site.com.testing/repos/site.com/trunk, you’ll see the last revision was revision 620 because it is talking to the server.
• If you did a svn update and then a svn info, you’ll see your working directory is at revision 620.

Just a quick question: Did you commit a few files, or did you commit the entire working directory? If you specified in your commit the files that were changed, this would make sense. Subversion wouldn’t have known to update the .svn/entries file in the root of your working directory. However, I’ve seen this even when I commit all changes. I’ve taken to doing an svn up whenever I commit all of my changes.

Remember: It’s not a bug. It’s a feature.

by David W. from http://serverfault.com/questions/380295