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

Re: Locking UI comments

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2004-10-13 23:07:48 CEST

--On Wednesday, October 13, 2004 3:26 PM -0500 "Brian W. Fitzpatrick"
<fitz@collab.net> wrote:

> I think we're once again running into the misunderstanding fostered by
> the name 'svn:lock' which should be something to the effect of
> "svn:this-file-must-be-locked-before-committing."
> The property is part of the communication system involved in locks--it
> has nothing to do with whether or not the file/path is locked.
> So I would say that locking/unlocking a file does not bump the revision
> number.

I think there's confusion about what I was referring to here.

The lockdiscovery property I was referring to is WebDAV's way of reporting
whether or not there is an actively held lock. This has absolutely nothing
to do with 'svn:lock' or 'svn:must-lock' or whatnot.

Take a look at RFC 2518 Section 13.8 for what I mean. WebDAV reports the
presence of a lock by responding to a lockdiscovery PROPFIND request. This
is how 'svn info' for a lock would likely be implemented over WebDAV.

So, back to my question: does the fact that the property of a resource
implicitly changes because a lock has been acquired or released also mean
that the global rev number also changes? By and large, our response has
been that if any property changes, so should the repository revision.
Although I feel that might not be appropriate here. I've found the WebDAV
and DeltaV specs to be completely unhelpful here. My hunch is that they
shouldn't (and is permitted by DeltaV), but I'm not 100% sure. I'm going
to ask some of the WebDAV folks around the office though... -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 13 23:08:18 2004

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.