David,
I think this is the same problem I reported a couple of weeks ago, which
turns out to be a non-problem. If you commit a folder which has changes in
sub-folders, you need to do an update on the parent folder before you can do
a branch/tag. The "out of date" message means you need to update.
I am not exactly sure what the update does - it does not change your files,
so I guess it is updating the .svn folder.
Simon.
"David Smith" <d.smith@ceoimage.com> wrote in message
news:E1BzHTk-0007Mw-00@deer.gmane.org...
> Our daily use of TortoiseSVN works fine, but we continually run into the
> same set of commit errors while tagging. I am branching
> "svn://ceont1/Basecamp .NET" to "svn://ceont1/branches/Basecamp .NET/Scan
> Docs 0.9.3.x", so the tagged branch is not beneath the project's trunk.
I'm
> including a screenshot of the error message whose text is shown below:
>
> Commit failed (details follow):
> Out of date: '/branches/Basecamp .NET/Scan Docs
> 0.9.3.x/Ceoimage.Basecamp/Basecamp/Search' in transaction 'ru'
>
> 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?
> Why aren't these files out of date when I do a simple commit? How can I
> prevent these problems in the future?
>
---------------------------------------------------------------------
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:08:32 2004