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

Re: Atomicity of locks and needs-lock

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-05-02 17:06:41 CEST

On 5/2/06, Mark Phippard <markp@softlanding.com> wrote:

> I will just add that the lock hooks were added to potentially assist with
> this as well. And I recall that mailer.py was enhanced to support sending
> lock messages if desired. This could assist with communicating locks.
> Agree with everything you said.

And in fact, I know a team of 5 people who are professional music
typesetters that use the lock hook for this. The use a program called
'Finale' to edit music scores, which saves its data in a proprietary,
binary, non-mergeable format. So they have the 'svn:needs-lock'
property proactively attached to every single score-file in their
repository. All the files are read-only by default. Additionally,
whenever they 'svn lock' a file to begin edits, the whole team
receives an email (just as they do when commits & unlocks happen.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 2 17:07:19 2006

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.