[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: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2004-10-13 23:44:11 CEST

--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

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:45:23 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.