"Bert Huijben" <[email protected]> writes: > This new configuration option assumes any client > (=libsvn_client/libsvn_ra_local user) wants to have the same caching. > > So a short lived 'svn' which exits after a single command has a > similar cache as a long living 'subclipse' or .... > > Is this really what we want?
Maybe, maybe not. Only people who want to change the default will have a problem, and then only if they want clients to be different. On a Linux system there is very little overhead to having a large cache for a short lived 'svn'. It's only likely to be a problem if memory is short and overcommit is not enabled. > The previous code specifically made this behavior different between > clients, while the one time initializing in sv_ra__local__open makes > it hard for clients to configure their own caching. (They can't do it > before calling into libsvn_client as it will be overwritten by this > new code) A client can set the value in the config, just as 'svn' does to override config values with command line values. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
