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

Re: svn commit: r11334 - in trunk/notes: . locking locking/old

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-10-12 21:38:50 CEST

On Oct 12, 2004, at 3:20 PM, Philip Martin wrote:

> sussman@tigris.org writes:
>> + - Clearcase dynamic views
>> +
>> + The workspace is always up-to-date, all of the time.
>> And
>> + it's impossible to circumvent the read-only bit. So the
>> + hijack scenario can't happen at all.
> As I understand your hijack scenario, a Clearcase unreserved checkout
> is equivalent to circumventing the read-only bit.
> Clearcase supports reserved and unreserved checkouts. There can only
> be one reserved checkout for each item, and such a checkout can always
> be committed. There can be multiple unreserved checkouts whether or
> not there is a reserved checkout. An unreserved checkout can be
> committed, or converted into a reserved checkout, provided there is no
> other reserved checkout and provided the item is not out-of-date. A
> reserved checkout can always be converted into an unreserved checkout.

Yah, I'm aware of all these options. I'm trying to keep things simple.

In particular, I'm focusing on a very common scenario -- a group of
"non" VC users are using VC in a 100% locking paradigm. Say, a bunch
of managers being forced to keep word docs in a repository, or a bunch
of web designers being forced to manage images in a repository. My
sources tell me that when such groups use Clearcase, it's pretty much
all reserved checkouts, and nothing else.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 12 21:39:07 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.