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

Re: Locking server implementation: libsvn_repos or libsvn_fs

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-11-02 19:57:36 CET

On Tue, 2004-11-02 at 13:46, John Peacock wrote:
> And if I have set an ACL to make trunk/notes/releases.txt readonly, then
> branches/1.1/notes/releases.txt should also be readonly if they happen
> to be the same node-rev?

You're right, that's a potential problem of conceiving ACLs as mapping
node-revs to access control lists. I don't know what the answer will

But this a tangent. I misunderstood what Fitz was saying; he just wants
the locking tree implementation to have a tree form so that it's fast to
query for "are there any locks within this subtree?" I wasn't talking
about the concrete implementation when I said the lock table maps
pathnames to locks, so we didn't have a real disagreement.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 2 20:00:52 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.