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

[PATCH] Clarify the semantics of file locking

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-01-18 14:51:04 CET

The locking functional specification is not completely clear. Do you agree
with this clarification and, if so, may I commit it?

(An alternative interpretation of the first part could be: "The restriction on
moving or deleting a locked file is a restriction on changing its membership of
its immediate parent directory. Thus, moving or renaming any parent directory
is still allowed as long as this file retains its current name within its
immediate parent.")

- Julian

Clarify the semantics of file locking.

* notes/locking/locking-functional-spec.txt

Index: notes/locking/locking-functional-spec.txt
--- notes/locking/locking-functional-spec.txt (revision 12757)
+++ notes/locking/locking-functional-spec.txt (working copy)
@@ -48,12 +48,21 @@ II. New Client Behaviors
           right to change the file's text and properties, to delete the
           file, and to move the file.

+ The restriction on moving or deleting a locked file is a
+ restriction on changing its full path name in any way,
+ including by moving or renaming or deleting any of its
+ parent directories.
+ (A locked file can still be read and copied, and any copy of it
+ will not automatically be locked.)
     B. Client requirements for locking

        1. Enforcement system

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 18 14:52:44 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.