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

Re: "svn lock" process return code (Subversion 1.2 RC2 Win32)

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-06-14 21:25:11 CEST

On Tue, 14 Jun 2005, Greg Hudson wrote:

> On Sat, 2005-05-07 at 13:15 +0200, Peter N. Lundblad wrote:
> > So if you say
> > svn lock a b
> > and a was already locked, it continues with b. If the latter lock
> > operation succeeds, should it return success or failer? Maybe someone on
> > dev@ has an opinion.
> Sure, I have an opinion. "svn lock a b" should return success if a and
> b are locked by the working copy upon completion.
> So, if a was already locked by someone else, the result should be
> failure. If a was already locked by this working copy, the result
> should be success.
Seems logicla to me. I think the problem is that the locking functions
choose to continue on some errors that should really be fatal. Seems like
this needs some reworking. Not sure if there is an issue for this.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 14 21:26:11 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.