Surely the getLock comments are the opportunity to explain why a file is
locked? I am only a novice, but if you HAVE to lock files, and someone else
is wanting to use them, shouldn't you explain why they are locked and by
whom so that communication between parties can start?
I only chuck my two pennies, as I am interested in this area due to some
requests from my development team who I am introducing this application and
process to.
Adam.
-----Original Message-----
From: Helge Richter [mailto:h.richter@insiders.de]
Sent: 26 November 2007 09:44
To: dev@tortoisesvn.tigris.org
Subject: getLock behavior...
We're using the locking feature extensively (all our files need lock)
and so we use the getLock-Feature quiet often. It's bit annoying that in
order to lock a file you need to first click away the comments dialog
(we do not use comments on getLock, only on commit) and then you click
away a confirmation-dialog (what purpose does this dialog fullfil?).
We'd love to see an option to disable getLock-Comments and the
confirmation-page so we could use getLock without any questions (if the
file is not already locked).
Would this feature be possible for a further release?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Nov 26 10:55:30 2007