"C. Michael Pilato" <cmpilato@collab.net> writes:
> But before even reading the patch or trying your test script, I was anxious
> to see how you would handle what I suspected would be a little booger of a
> programming challenge, namely dealing with the situation where you have two
> changes that are more than one depth level apart, yet individually specified
> on the 'svn commit' command-line with different depth levels:
>
> $ svn st
> M A/D/G/rho
> M iota
>
> Now, I try 'svn ci' with various depths that I think should catch both
> changes. The following two combinations don't work:
>
> $ svn ci --depth immediates . A/D/G
> subversion/libsvn_wc/lock.c:561: (apr_err=155004)
> svn: Working copy '/home/cmpilato/tests/karl-patch/wc' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
> $ svn ci --depth immediates . A/D/G/rho
> subversion/libsvn_wc/lock.c:561: (apr_err=155004)
> svn: Working copy '/home/cmpilato/tests/karl-patch/wc' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Fixed in r26487.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 6 22:07:46 2007