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

Re: Locking consensus(es) so far

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2004-10-13 23:58:07 CEST

On Oct 13, 2004, at 5:44 PM, Justin Erenkrantz wrote:

> --On Wednesday, October 13, 2004 2:24 PM -0700 Justin Erenkrantz
> <justin@erenkrantz.com> wrote:
>> As I've pointed out earlier, lots of reasons. It's a file that could
>> have a lot of contention or needs to be modified in such a way to
>> ensure
>> no two people commit to it at the same time. But, I wouldn't assume
>> that
>> svn:needs-lock (or must-lock) is only set on unmergable files. --
>> justin
> Here's a real use case to ponder: Dreamweaver's WebDAV interface
> requires that all files (HTML, etc, etc.) be checked out before
> editing. However, the Subversion clients (say a part of the group
> wasn't interested in using Dreamweaver) would need the 'svn:must-lock'
> property set on those files in order to know that the files must be
> locked before editing them in order to play well with the Dreamweaver
> users. -- justin

So, why would a group of people uninterested in Dreamweaver start
editing those files, or even care if they're locked at any given time?

And beyond that, assuming Dreamweaver files are unmergeable, doesn't it
make sense for the admin to set 'svn:needs-lock' on them anyway? That
way, even when the Dreamweaver folks aren't using Dreamweaver, they're
less likely to accidentally change the file contents.

What's the problem here?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 14 00:00:17 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.