Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup

Branko Čibej wrote: > Please file a bug with the reproduction script. OK, the issue number is SVN-4642. Thanks

Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup

Branko Čibej writes: > I can reproduce this with 1.9.4 and trunk ... definitely a bug, only > dir/subdir2 should be left (since dir/subdir2 is unversioned content of > dir). Thanks Brane. Would it be possible for an svn dev to take this on? By the way, I just checked it with 1.8.16 and everything

Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup

> This must be a bug, right? Any chance somebody can take a look at it? [... tumbleweed ...] Anyone? Should I file a bug report? Thanks

"svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup

When excluding a subtree from the working copy, if any unversioned items are present then the svn update command fails silently, leaving the working copy locked and requiring cleanup. This is with version 1.9.4, the current release. Reproducing the problem is fairly straightforward. Create a ne