Kirk Lapray wrote:
> I have looked through the mailing list and all bug reports and have not
> seen this problem mentioned. I might have overlooked it, and if so,
> please disregard this report.
>
> Whenever a file is deleted or renamed using the TortoiseSVN tools and
> then committed with "keep locks" selected the server keeps a lock on
> these files even though they no longer exist. So, if at any time in the
> future you try to add a file that has the same name as one of these
> previous files you get a "file already exists" error. This also has the
> possibility of leaving a lot of locks on the server that I would think
> are unnecessary.
>
> To me it would seem to make sense to always remove the lock on files
> that are deleted, even if "keep locks" is selected. On files that are
> renamed remove the lock on the old file and get a lock on the new file
> if "keep locks" is selected.
>
> I am not sure how hard this would be to implement, or if there is a good
> reason why it is not like this. I have had some problems with it lately
> and ended up cleaning almost 600 locks up for files that no longer exist
> in the repository.
Reported with reproduction recipe on the Subversion mailing list.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Feb 18 14:07:15 2006