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

RE: Re: Locking

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-14 20:03:07 CET

> -----Original Message-----
> From: Erik Huelsmann [mailto:ehuels@gmail.com]
> > Oh, and to deal with the user's statement that "Subversion must be
> > broken.." If svn status -u or svn get-lock return a statement or
> > value that lets user know that "File X was locked since
> working copy
> > was last updated" then the user can't say that subversion
> was broken.
> > Then you prevent your error case *AND* provide the maximum
> data value.
> But locks are transient - unversioned - data. There's no way
> to know the lock existed before the update: they're not
> related to revisions in any way.
> bye,
> Erik.

Erik, I don't understand why that is relevant. The idea is to show the
state of the server, isn't it? Perhaps you're thinking about the
concept of "revert to revision", where you're "updating" to a non-head
revision. Is it a problem? Why does it matter that locks are

This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 14 20:03:37 2007

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

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