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

Re: Directory locking: current goals

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-10-16 19:33:58 CEST

Branko ╚ibej <brane@xbc.nu> wrote on 10/16/2004 12:09:54 AM:

> Mark Phippard wrote:
> >The only "high-end" tool we
> >seem to talk about is ClearCase, of which I have no direct experience.
> >has been said you need to have a lock on a directory in CC in order to
> >or delete files in the directory. This seems ridiculously limiting to
> >and strikes me as just a deficiency in their model for versioning
> >directories.
> >
> Huh? ClearCase is merely being consistent. Adding to or removing files
> from a direvtory is analogous to changing the contents of a file, and
> since CC requires you to "check out" a file in order to change it,
> having the same requirement for directories makes sense. CC's directory
> lock is exactly equivalent to the Unix write permission bit on

As I said I have no experience with ClearCase, so if these conclusions are
wrong, let me know. As I read this feature if you have to checkout a
directory to add a file, then it would follow that if someone else has the
directory checked out already, you cannot add a file. So, regardless of
whether it is consistent, if this design does not allow more than one
person to add files to a directory at the same time, I do not think it is
very good design. That is all I meant.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 16 19:34:12 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.