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

Re: Locking: RFC: svn:needs-lock behaviors (Updated)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-04 04:35:59 CET

On Feb 3, 2005, at 6:56 PM, Branko Čibej wrote:

> Greg Hudson wrote:
>> On Wed, 2005-02-02 at 17:49, Philip Martin wrote:
>>>> Propset:
>>>> - Setting the svn:needs-lock property sets the file to read-only
>>>> (It also canonicalizes the value to '*')
>>> 1. Not if the file is locked in the current wc.
>>> 2. What about schedule add files? I don't think they can be locked
>>> so
>>> they should remain read-write.
>> To the best of my knowledge, you should be able to lock schedule-add
>> files just fine. Locks apply to pathnames, not nodes or node-revs.
> DAV lets you do that, yes, but AFAIK we decided not to allow it.

Funny, since I implemented it last month. :-)

It's pretty important to me that we end up with a "finished"
autoversioning feature as a side-effect of all this locking stuff.
That means allowing locks on nonexistent paths, and allowing a client
to create an expiring lock. If we don't have those things, some very
popular DAV clients won't interoperate.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 4 04:39:06 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.