RE: Re: Problems with exclusive-locking
From: bugreport <M8R-fj4tn21_at_thisisnotmyrealemail.com>
Date: Thu, 27 Feb 2014 23:02:43 -0800 (PST)
Hi Stefan, thank you for your reply.
To the performance increase Apache seems to have different test results:
> The only reason to enable this is to get a small performance boost, and
> Exclusive SQLite locking of working copies
Why do you think does Apache put this into it's release note, proclaiming a significant performance gain?
I'm aware that placing working copies on network drives (in our case a SAMBA net share) is not the way it should be done, but I'm not in the position to change this internal order. The svn commit/svn update procedure for getting this on the build machine would result in the need for every developer having an own branch as trunk, where current commits go, is near-to-clean and always has significant tests before it's updated - and you need to compile it (only possible on the build machine) before you can test it or get a compiler error...
Thank you for the explanations why exclusive locking currently does not work with TSVN.
These are my open questions, that are open even with the background that TSVN will not support exclusive locking:
1. Is it possible (in a later release) to somehow *end* the current svn command (and therefore the log) without exiting the TSVN process handling the update dialogue? This question comes to mind especially as it works in the commit dialogue, locking only as long as there is a refresh.
2. Can the timeout for the context menu be set (and reduced) by TSVN [maybe set via TSVN->settings or svn config file]? The timeout occurs much faster when using the command line tools.
3. Can TSVN react *clean* on this timeout in the following scenarios:
Thank you for answering these points.
BTW: It's nice that the Overlays work quite well with exclusive-locking enabled. But the overlays are very likely the reason why there was a random sqlite[s5] two times on TSVN->update.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
This is an archived mail posted to the TortoiseSVN Users mailing list.