Deploying registrar configs in a BC safe way

[Boris Feld]

On Wed, 2017-10-25 at 21:33 -0400, Augie Fackler wrote:
> A wrinkle I noticed in hgsubversion tonight: I've got a fair number
> of config items whose default is `None`, but the config registrar
> treats a default of None as no default and requires specifying a
> default explicitly.

That's weird, can you provide us with an example of code and what you
get?

We have several config items registered in core with None as default
and it doesn't emit a devel warning.

Do you have any code in hgsubversion that would interfere with the
config system?

Cheers,
Boris