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

Re: About the discussion of 'I need another overlay for 'locked by others''

From: Andy Levy <andy.levy_at_gmail.com>
Date: Thu, 17 Jan 2008 07:00:49 -0500

On Jan 17, 2008 5:15 AM, zero5870 <zero5870_at_gmail.com> wrote:
> Abou this discussion of bellow, is any possible to get the file lock
> information form repository

Yes, but as is noted in the explanation, it requires contacting the
repository. TSVN (and all SVN clients) connect to the repository as
little as possible.

> when we use 'SVN Update' command, and display a new overlay to emphasize it.
> (or make it optionally)

As soon as svn up completes, any information that as downloaded may be
out of date and invalid. Locks especially can be very transient.

> ** If we can set some new overlay to emphasize the file had been locked(or
> modified but not commited)

You will never know if another WC has changes that haven't been
committed, because that information is never communicated to the

> by someone else at 'SVN Update', it will be more efficiency than specially
> use 'Check for Modifications' I think.

No, it's less efficient, and would put undue load on the network and server.

Things are done the way they are for very, very good reasons which
were explained in what you copied & pasted into your email. It's not
going to change.

> There is no way to tell if a file has been locked by someone else, so I need
> a new overlay to show that.
> Unfortunately, that's not possible. Locking information is held in the
> repository, so in order to refresh the page in explorer, we would have to
> contact the repository. That would make explorer impossibly slow. Servers
> often take several seconds to respond, sometimes minutes - do you really
> want explorer to hang while that takes place, every time you open a
> versioned folder?
> A fundamental design feature of TortoiseSVN is that the repository is never
> contacted except when explicitly requested by one of the context menu items.
> Even with that restriction, it is still hard work maintaining a fast
> response.
> If you use locking to prevent simultaneous editing, then you should consider
> using the svn:needs-lock property. Read the locking section in the manual to
> learn how to use this property. That way, files in your working copy will be
> read-only and have a grey overlay until you acquire a lock.
> If you want to see which users have files locked in their working copies,
> use the Check for Modifications dialog and click on the Check repository
> button.
> Best Regards.
> zero5870

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-17 13:01:00 CET

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

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