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

RE: Re: Feature request: Warning on get lock

From: Edward Harvey <eharvey_at_chilsemi.com>
Date: 2006-05-09 02:09:49 CEST

> From: Tobias Schäfer [mailto:tobiasschaefer@gmx.de]
> I've implemented this feature, see attached patch and screenshot.

Excellent response time on that. :-) I think this is good -- Since "check for modifications" is the only present way to discover someone else's lock, this info balloon encourages people to use 'lock' and 'needs-lock' together, which will improve communication of locks and better lock habits.

A couple of comments --

Is there a checkbox that disables the balloon if you want to? (I haven't looked yet, please forgive me if that's an obvious question.)

AFAIK, the subversion folks and tortoisesvn folks seem to accept the idea of caching the most recently known lock status, for locks that are owned by other users.

When and if that information is stored locally, I hope to add some checkboxes in tortoisesvn like this (unchecked by default, to preserve present behavior) --

        Files that are locked by other users,
        at the time of the most recent local update:
                [X] Use the gray icon
                [X] Make the file read-only

        [X] It is ok to lock files that don't have the
            needs-lock property. Don't warn me.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue May 9 02:10:08 2006

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.