RE: Working copy corrupted by branch deletion
From: Bert Huijben <bert_at_qqmail.nl>
Date: Sat, 19 Jan 2013 22:59:14 +0100
Thanks for a very interesting issue to look at.
I'm happy to report that I would now call this issue fixed:
I think we can call this a known issue as it has been known for quite some
A workaround for this issue would be to do an explicit update of the missing
I documented the issue as issue #4295 with the following recipe
$ svnadmin create repos
$ svn mkdir --parents file:///%CD%/repos/A/B/C -m ""
$ svn cp file:///%CD%/repos/A file:///%CD%/repos/AA -m ""
$ svn co file:///%CD%/repos/A A
$ svn switch ^/AA/B A/B
$ svn rm file:///%CD%/repos/AA
$ svn up A
On 1.7 this reproduces your issue
$ svn up A/B
Will bring back the missing directory.
When trying the same thing on trunk I found a completely different issue,
To close issue #4295, I added a small check to the update code that handles
I will nominate the fix for backporting to a future 1.7 release.
From: Maxwell Ballenger [mailto:Maxwell.Ballenger_at_spacex.com]
Hi Subversion Users,
We're experiencing some new behavior after upgrading from TortoiseSVN 1.6.14
1. Branch a subfolder of your working copy
In TortoiseSVN 1.6.14 (Subversion 1.6.16), a mistake like this was much
Is this intended behavior, or could it qualify for a bug fix? Does anyone
This is an archived mail posted to the Subversion Dev mailing list.