On Fri, Apr 23, 2010 at 08:38:01PM +0200, Matthias Hryniszak wrote: > Thanks for the response - that's really great to hear and I guess I'll skip > this one in that case.
On second thought, you can still file an issue, with the intention that this particular use case will be tested and verified to work before 1.7 release. To facilitate this, can you provide a reproduction script (UNIX shell or Windows cmd, whichever you prefer) which starts by creating an empty repository and runs svn and other commands until the problem is triggered? That would help greatly. We could use this script to reproduce the problem with 1.6, and later verify that the problem is gone in 1.7. We could even add a regression test to our test suite based on your script. (A script is great for this because it is a lot easier to convert into a regression test than English prose.) Thanks, Stefan
