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

Re: File lock issue

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 2 May 2008 07:06:04 -0400

On Fri, May 2, 2008 at 4:00 AM, Srilakshmanan, Lakshman
<lakshman.srilakshmanan_at_police.vic.gov.au> wrote:
> I find that a file with svn:needs-lock creates an exclusive lock only in the
> branch I am working in.

Right, because once you make the branch, each copy is a separate
entity in the repository and they are not connected going forward.

> My understanding was that creating an exclusive lock was to ensure
> serialised update on files (eg word docs) because they cannot be merged.

That's one *use* of locks, but it's not a guarantee, as any user can
steal the lock unless you put in a pre-lock hook script to prevent it.

> Is there any way of preventing changes across branches till the latest copy
> of the file is merged into the branch before editing or alternatively is
> there a way of informing users on different branches that the file has been
> edited and they need to update their copy before proceeding.

Send out an email when the lock is created, perhaps? Manually lock each copy?

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-02 13:06:34 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.