[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: Patrick Dean Rusk <PRusk_at_foliage.com>
Date: 2004-05-21 21:10:42 CEST

"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.

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.

My apologies if these thoughts have already been expressed. I've had a hard
time keeping up with the number of messages on this topic.

Patrick Rusk

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:20:30 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.