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

Re: Revised Proposal: Improved locking implementation for fsfs

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-01-06 20:20:40 CET

Ben Collins-Sussman <sussman@collab.net> writes:

> I think what they're saying is: "we'd like to *require* locks on
> every file in the repository before editing", right? Not that they
> literally want to attach an active lock to every file in the
> repository at the same time.
> In other words, when they import a project, the first thing they'll do
> is attach the new 'svn:needs-lock' property to every file.

Once svn:needs-lock is set on all files any global change, an updated
copyright say, will require all the files to be locked. I think it's
safe to say that some users will set svn:needs-lock on all files and
will then attempt to attach an active lock to every file.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 6 20:21:55 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.