[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: exit codes and locking

From: Jim Correia <jim.correia_at_pobox.com>
Date: 2005-04-08 22:18:19 CEST

On Apr 8, 2005, at 4:20 PM, Peter N. Lundblad wrote:

> On Fri, 8 Apr 2005, Julian Foad wrote:
>
>> Jim Correia wrote:
>>> Is (our should) subversion be consistent about returning non-zero
>>> exit
>>> codes when an operation failed?
>>
>> Yes, absolutely it should, and I believe it is pretty consistent. Any
>> deviation is a bug.
>>
> ...
>>> However, if I attempt to lock a file that is locked in another
>>> working
>>> copy, it fails with an error message, but the exit code is 0.
>>
>> Bug. Thanks for reporting it.
>>
> What should we return if some locks are successfully acquired and some
> not? The reason this happens is because it is handle by the
> notification
> system. I think the same happens for a failed revert, but I haven't
> tested. Don't we have other commands that will just print an error
> message
> and continue?

svn revert fileThatDoesNotExist

reports:

Skipped 'fileThatDoesNotExist'

and returns 0.

If that is the expected behavior (and eventually becomes documented to
be so) that's ok by me. I just wanted to make sure that was the
expected behavior in this case.

(The rm case seems worse because it silently succeeds - if it printed a
warning that would be better - issue filed.)

Jim

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 8 22:19:23 2005

This is an archived mail posted to the Subversion Dev mailing list.