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

Re: svn commit: r1801940 - in /subversion/trunk: ./ notes/ subversion/include/ subversion/include/private/ subversion/libsvn_delta/ subversion/libsvn_fs_fs/ subversion/libsvn_subr/ subversion/tests/libsvn_delta/ subversion/tests/libsvn_subr/

From: Stefan Sperling <stsp_at_elego.de>
Date: Wed, 26 Jul 2017 13:50:37 +0200

On Wed, Jul 26, 2017 at 02:41:31PM +0300, Evgeny Kotkov wrote:
> Stefan Sperling <stsp_at_elego.de> writes:
>
> > Sounds like we're headed in a good direction :-)
>
> One particular thing that bothers me about using LZ4 as the new default
> is that I think that a decision like that goes a bit against the usual policy
> (add new optional feature, switch the default in the next minor release).
>
> But, personally, in this case I would say that it would make sense to
> immediately make LZ4 the new default and available to the users, if there
> won't be objections to that.

If our test suite passes with lz4 I see no reason for concern about
making it the default right away.

> I think that the proposed solution with the new option that overrides (and,
> essentially, deprecates) 'compression-level':
>
> compression = none | lz4 | zlib | zlib-1 ... zlib-9
>
> is explicit and should be understood by the users in case they stumble
> across it.

Makes sense.

> Please note that I don't think that we should change the behavior of
> 'compression-level' in fsfs.conf. In other words, the 'compression-level'
> would still mean "zlib compression level", exactly as it works now.

Sure. Very explicitly deprecated, please. If an option is marked deprecated
then admins can tell they don't need to waste time thinking about it.
Received on 2017-07-26 13:52:29 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.