Re: svn commit: rev 5814 - in trunk/subversion: libsvn_wc tests/clients/cmdline

cmpilato@collab.net writes:

> Philip Martin <philip@codematters.co.uk> writes:
>
> > I agree it could be solved there, but solving it on the client side
> > means that every client has to be aware of the problem and has to find
> > a solution.
>
> Well, yes, but that's why we have a librarized implementation. These
> changes all live in libsvn_wc -- I dunno anybody crazy enough to write
> their own libsvn_wc library.

We have more than one implementation. I think switch shares the
update implementation, but consider

  'svn diff -rX'

where there is a missing item in the working copy that has been
deleted in revision X. Do we need to modify the diff client to handle
this case? (Do we even know what it should do? I think the diff
command should indicate the deletion, but it would not surprise me if
other people thought differently.)

Then there is 'svn status -u', do we need to modify that client as
well?

Eeek! I've just come across a bug while trying that status command

svnadmin create repo
svn mkdir file://`pwd`/repo/foo
svn rm file://`pwd`/repo/foo
svn co -r1 file://`pwd`/repo wc
svn st -u wc
../svn/subversion/libsvn_wc/lock.c:488: (apr_err=155005)
svn: Working copy not locked
svn: directory not locked ()

Oddly enough 'svn st -uv wc' works.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org