Re: [PATCH] Extending r15287 for issue #2264

> Also, it doesn't seem possible to set up a Python test case for the code
> changes using this scenario:
>
> 1 lock a set of files
> 2 unlock a single file
> 3 unlock the entire set of files
>
> The client would say the unlocked file is already unlocked and not
> proceed further. Any suggestions would be much appreciated.
>
The client is not skipping the non-fatal error. I tested this with
   svn, version 1.3.0 (dev build)
   compiled Sep 16 2005, 02:50:10
$ svn st -v
      K 1 1 vivek file1
                1 1 vivek file2
                1 1 vivek file3
But :-
$ svn unlock file2 file1
subversion/libsvn_client/locking_commands.c:341: (apr_err=195013)
svn: 'file2' is not locked in this working copy
$ svn st
     K file1
There are other commands which needed this skipping when non-fatal
errors were encountered. I am sorry I was committed to this but was
busy with other priorities.

Thanks,
Vivek
> Regards
> Sameer
>
>

----------------------------------------------------------------------------

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