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

Re: weakness in locking UI

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-01-04 18:16:43 CET

On 1/4/06, Mark Phippard <markp@softlanding.com> wrote:

> I have mixed feelings. When you try to lock a file, it will fail and tell
> you who has it locked. Why did I really need to see this info before
> attempting to lock the file? What difference would it have made?

I think we're talking about different problems here. My users aren't
so worried about seeing the latest repository-lock information as they
casually browse through Finder or Explorer, but they *would* like an
easy-to-run command that gives a 'locks report': "here are all the
current locks, and all their details".

> What if svn info, when run on a local WC file, had an option to get the
> latest server information? This could then show you the current lock
> information from the repository, as well as if the file were out of date.
> GUI's could possibly use this as a way to provide an option users could
> use to check the information for a file before locking it.

This would certainly fix the annoying "have to type the whole URL"
problem that 'svn info URL' presents. But I still think we need the
ability to fetch a locks-report somehow. Maybe it's as simple as 'svn
st -u' getting a lock-owner field.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 4 18:18:21 2006

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.