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

Re: Feature / Bug - File lock icon, checking for modifications

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-04-23 15:56:17 CEST

Edward Harvey wrote:
> I've seen a lot of discussion from various people here, regarding file
> lock icon not appearing, and I've seen a degree of resistance, based on
> the argument that file locking is a local operation, and you have to
> contact the repository to see if someone else has a lock.

I wouldn't call good arguments against something 'resistance'.

> Feature request -
> There is presently no icon indicating that a remote person has a file
> lock, and there should be. Of course such a thing would be the most
> useful if there's a way to silently periodically check for
> modifications. Likewise, there is no icon indicating that the local
> file is out-of-date (modified and committed by a remote person), and
> there should be.

No, there should not be such an icon. If you really read about this in
our mailing lists, you would know why. We even have a FAQ entry about this:

* It takes a long time for some servers to respond. Which would make the
overlays slow, and therefor the explorer way too slow to work with.
* There are only 12 overlay slots available in explorer, and those 12
slots have to be shared with *all* applications. Adding two more to TSVN
would either make other apps not show their overlays, or TSVN couldn't
show them because other apps already use the available slots.
* You can use the post-lock hook script to send out a mail to every
developer if you want to know who has which files locked.
* You can use the post-commit hook script to send out commit mails. Then
you know that a file is out-of-date too.

> If this suggestion isn't met with too much resistance, I'd like to
> encourage someone to work on it, and if that doesn't happen, I'd like to
> consider the option of working on it myself. (I'm no great programmer
> and hence inclined to let someone else do it if they care to, but at
> least I can usually understand something I read in source code.)

You can of course work on such a feature yourself. But be prepared to
have your patch rejected if it slows down the explorer.


Your mail subject reads "Feature / Bug -...". Even though you *know*
that this isn't a bug, you still claim that in your mail subject. Why?
Why is everything people don't understand a bug? People doing that don't
get a lot of sympathy points from me...

   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sun Apr 23 15:56:35 2006

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