Resource out of date try updating tortoisesvn

10 Jan

Whenever a change on a file is committed, the revision of the parent directory changes in the repo, but you working copy still has the directory in its old revision.

So in your scenario after adding the file the parent directory in the repo has a higher revision than your working copy.

If I understand subversion correctly, the problem is this: Subversion tracks the current revision for each file and directory separately.

You may have had a commit that went sour between the time the new revision was added in the server and the time your client performed its post-commit admin tasks (including refreshing your local text-base copy).

This might happen for various reasons including (rarely) problems in the database back end or (more commonly) network dropouts at exactly the wrong time.

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.