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

Re: Feature Request - Locking

From: Mark Phippard <markp_at_softlanding.com>
Date: 2005-12-01 22:56:51 CET

"David Keeley" <dkeeley@bravurasolutions.co.nz> wrote on 12/01/2005
04:04:12 PM:

> We use tortoise as a key tool in our organization, the primary gateway
to
> subversion VCS. It is great.
>
> We use locking on many of our binary files (not on anything that lends
itself
> to concurrent modification).
> The primary purpose of this is not to prevent other users from changing
the
> file while you are but to alert them that you are currently making
changes so
> they don’t start doing that either. Unfortunately tortoise does not
meet that
> requirement as you can not see (by icon or other status indicator) if
someone
> else has a file locked in the standard explorer view of the files.
Obviously
> this would only happen if the last time the file was updated it was done
so to
> HEAD. Even if this graphical indicator just meant ‘was locked by jblogs
at
> last time this file was updated’, that would be very useful and making
the
> locking experience we have with subversion as good as it was with other
> version control systems that have locking.
>
> Please advise if this makes sense and if a enhancement request comes of
it.

It makes some sense but it just isn't going to happen.

1) TortoiseSVN cannot contact the server for decorators. Performance
would be insane. It isn't even that great getting the info locally.

2) Subversion does not store the information on other locks in the WC.
TortoiseSVN cannot do stuff that Subversion does not support. So you
would have to convince the Subversion developers to make this a Subversion
feature.

3) Your request is slightly bogus, in that you exaggerate the problem. You
say that you want to alert users that you are making a change so that they
do not start making a change. OK, but the first thing they have to do to
make a change is acquire the lock, at which point they will see this
information. So hasn't locking in fact fulfilled its purpose? Seeing a
decorator that could in fact be wrong could really be worse, as the user
might not attempt to acquire the lock on a file that has been updated.

4) Locking can be supplemented with hook scripts that send emails when
files are locked or unlocked. This can be your proactive communication.

5) Finally, the TSVN repository browser shows active lock information.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Dec 1 23:05:47 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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