On Wed, May 27, 2020 at 02:56:34PM +0200, Magnus Hagander wrote:
> Seems like the better choice yeah. Since we're changing the default anyway,
> maybe now is the time to do that? Or if not, maybe have it log an explicit
> deprecation warning when it loads a config with it?
Not sure that's worth it here, so I would just remove the whole. It
would be confusing to keep the past values and have them map to
something we think is not an appropriate default.
--
Michael