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

Re: svn commit: r9875 - trunk/notes

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2004-05-27 15:45:56 CEST

sussman@tigris.org writes:

> Author: sussman
> Date: Mon May 24 12:59:48 2004
> New Revision: 9875
> Added:
> trunk/notes/locking-design.txt (contents, props changed)
> Log:
> * locking-design.txt: new file. Begin a design document for group to hack on.

> +A "lock" means a (possibly shared) write-lock on a file or directory.
> +When a file or directory is locked, only the lock-holder(s) may commit
> +a change to it.
> +
> + - In the case of files, "commit a change" means changing a file's
> + text or props, deleting it, or moving it.
> +
> + - In the case of directories, "commit a change" means changing the
> + directory's props or entries-list, deleting it, or moving it.
> + This also applies recursively, to all child directories & files.

Clearcase has "locks", they are called "reserved checkouts". The
model is a bit different to the one proposed above.

A file lock allows the user to commit a new version of the file, that
would be a text/property change in Subversion. A directory lock
allows the user to commit a new version of the directory, one that
adds or deletes items in the directory, in Subversion it would also
allow directory property changes. In particular note that it is not
necessary to lock a file (or directory) to be able to delete it, one
must lock the parent directory instead.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 27 15:46:17 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.