On Mon, 2009-11-30 at 10:33 +0000, Philip Martin wrote:
> Philip Martin <[email protected]> writes:
>
> > I believe so. The problem is that the mkdir --parents call is leaving
> > the working copy locked:
Let's check the status in basic_tests.py 7:
[[[
Index: subversion/tests/cmdline/basic_tests.py
===================================================================
--- subversion/tests/cmdline/basic_tests.py (revision 885369)
+++ subversion/tests/cmdline/basic_tests.py (working copy)
@@ -325,6 +325,13 @@
svntest.actions.run_and_verify_svn("mkdir dir/subdir", None, [],
'mkdir', '--parents', Y_Z_path)
+ expected_status = svntest.actions.get_virginal_state(sbox.wc_dir, 1)
+ expected_status.add({
+ 'Y' : Item(status='A ', wc_rev=0),
+ 'Y/Z' : Item(status='A ', wc_rev=0),
+ })
+ svntest.actions.run_and_verify_status(wc_dir, expected_status)
+
#----------------------------------------------------------------------
def basic_corruption(sbox):
]]]
> This whole --parents stuff is bonkers. If I do
>
> svn mkdir --parents wc/foo/bar/zig/zag
>
> to create foo, foo/bar, foo/bar/zig and foo/bar/zig/zag the first path
> to get locked is wc/foo/bar. It makes no sense to start in the middle,
> either it should be locking paths from parent to child or from child
> to parent.
Eww. How did you observe that? Can you see source code that would do
that?
- Julian
