Deploying registrar configs in a BC safe way

[Augie Fackler]

> On Oct 26, 2017, at 2:41 AM, Boris Feld <boris.feld at octobus.net> wrote:
> 
> 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?

Can’t figure it out.

> 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?

Nope. I’ve come up with a crude-but-effective mechanism in hgsubversion to get things working. I also found a pretty awful interaction between lazy-generated repo objects and commitctx() in the process, which I’ll file a bug about shortly.

> 
> Cheers,
> Boris

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20171029/40ea1e32/attachment.sig>