David Smith wrote:
[snip]
> Commit failed (details follow):
> Out of date: '/branches/Basecamp .NET/Scan Docs
> 0.9.3.x/Ceoimage.Basecamp/Basecamp/Search' in transaction 'ru'
"Out of date" means: update your working copy first.
> I can only assume that we get commit errors when tagging but not when doing
> simple commits because tagging transactions include so many more files and,
> therefore, has a greater chance of being interrupted. But what interupts it?
It's not interrupted, it's simply rejected.
> Why aren't these files out of date when I do a simple commit? How can I
> prevent these problems in the future?
Out of date means that someone else (or you) committed a change. Note:
if you do a commit, the revision numbers of the modified and committed
files in your working copy change accordingly, but not the revision
numbers of the parent folders. So if you commit a change in a file which
creates e.g. revision 100, then you modify some folder properties and
try to commit them, you will get an "out of date" error message because
the folder revision isn't at 100 but e.g. still at 50 where you last
changed it. But if you update your working copy, then all folders get
the new revision.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Aug 23 20:28:30 2004