Greg Hudson wrote:
> (Also, how did you imagine that r10788 would pose no risk to the client
> if we don't activate svn_utf_initialize()? How would
> svn_utf_initialize() do any good if we didn't change the code path of
> actual translation functions? As it turns out, it looks like we might
> experience significant performance degradation if we don't call
> svn_utf_initialize().)
I just thought that since it was mentioned in the issue. The comment
there said that a change this big would require another RC release
first, but since that's not likely going to happen I thought not
activating it would at least not endanger the command line client but
still give TortoiseSVN the chance to use it.
And yes, the performance without caching the translation functions (keep
the so files loaded and reuse them instead of loading/unloading them) is
really, really bad.
>>Also, on a different subject: the crash in 'svn st -u' I reported for
>>the fourth time here:
>
> I took the ten minutes to figure out what was going on here and checked
> in a fix (r10841). I'll nominate it for 1.1.
>
> Of course, it's also a big problem that we don't have enough safety
> checks in "svn switch --relocate".
Thanks for that!
(nagging works!)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 6 21:17:46 2004