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

Re: Lock forced when out of date and updated

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: 2007-08-10 00:17:04 CEST

On 09/08/2007, Matthias Bendewald <matthias.bendewald@gmx.de> wrote:
> Situation:
> My working copy file is unchanged but out of date. I already locked it in another working copy.
> I try to lock it by right-clicking and selecting "get lock"
> I get a error message and a box, asking if i want to update the file and lock it then. I accept it.
> Expected:
> The file is updated and an error message is shown because the file is already locked.
> Actual Result:
> The file is updated, the actual lock stolen and i dont get informed about what happened to the lock.

Just to clarify, you are saying that there is no warning that the file
is already locked elsewhere, the lock is just silently stolen?

I just tried that with a recent nightly and I get an error message
when I try to update, saying that the file is already locked.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Aug 10 00:15:18 2007

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.