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

[Fwd: Re: Locking branch has been merged [Re: svn commit: r13571]]

From: Brad Kittenbrink <brad_at_windwardmark.net>
Date: 2005-03-22 20:08:28 CET

sorry, forgot to cc the list

-------- Original Message --------
Subject: Re: Locking branch has been merged [Re: svn commit: r13571]
Date: Tue, 22 Mar 2005 14:07:33 -0500
From: Brad Kittenbrink <brad@windwardmark.net>
To: Ben Collins-Sussman <sussman@collab.net>
References: <200503220532.j2M5WLS16319@morbius.ch.collab.net>

Ben Collins-Sussman wrote:
> On Mar 22, 2005, at 11:07 AM, Brad Kittenbrink wrote:
>> Is there a way (or a way planned) to require a user to hold a lock
>> token in their wc in order to read a file?
> How would this work? How could any part of Subversion possibly prevent
> some random editor from reading a file or changing the file's permissions?

The only way I would imagine it is to not actually put the data there
until the lock is acquired. For example, store the unlocked file in the
wc as a zero-length read-only stub file or something. When the user
acquires the lock, copy the contents over from .svn/text-base/ to allow
read/write access.

Obviously most users of locking would probably not want this
functionality, but if configured properly, it seems like a way to
enforce serialization for hijacking editors.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 22 20:18:06 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.