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

Re: Exclusive Locking: 2nd draft

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-05-21 21:30:06 CEST

"Patrick Dean Rusk" <PRusk@foliage.com> writes:

> "C. Michael Pilato" <cmpilato@collab.net> wrote:
> > IMO, this whole feature is a bust if I have to wait until after I've
> > uploaded the changes to my 20-Mb Word Document to find out that my
> > commit is denied because someone has that file locked. (Ben, I know
> > you agree with me ... just wanted to publicly state this opinion.)
> Perhaps this is moving into client-side issues too early, but it would be
> handy if an update would make read-only a file that someone else has locked.
> That would help someone to not make the mistake above.

(FWIW, I don't think we can fully have the server-side discussion
without talking about client-side UI anyway, so...)

> As a companion thought, it would be nice to be able to add a property to a
> file that marks it as needing to be explicitly locked in order to be
> committed. That would mean that whenever you update the file, it would be
> marked read-only, even if no one has yet locked it.

This is a feature I wanted, too.

I seem to recall others wanting the opposite -- read-only everything
unless you have the lock. But I think that's silly, and would make
Subversion into just another SourceSafe.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 21 21:30:54 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.