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

Re: Read-only checkouts/updates

From: Ron Gilbert <lists_at_rzweb.com>
Date: 2005-06-08 20:55:36 CEST

Ben Collins-Sussman wrote:
> On Jun 7, 2005, at 4:22 PM, Rick Mann wrote:
>> Is this being considered for short-term implementation, and if not,
>> why not? If it's a reasonable request, should I add an Issue for it?
> It's not being considered for short-term implementation, because it's
> just not our UI model. Subversion, like CVS, is a concurrent system
> based on copy-modify-merge. The UI you're describing sounds
> something very much like SourceSafe or PerForce, where everything is
> read-only by default, and you have to 'declare' intent to edit
> somehow. That UI contradicts the design philosophy of Subversion.
> Do you really have problems "accidentally" modifying files? I've not
> heard of such a thing before.

I have a very similar problem. I have a lot of non-technical people that need read-only access to the files, and, yes, they modify them all the time when they shouldn't be. Having them come down as read-only would solve about 99% of that problem.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 8 20:58:06 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.