comparison mercurial/configitems.py @ 34831:44c4ed4ad032

configitems: move rebase config into core The shelve extensions import and call rebase content without loading the extension. This is problematic as the config items rebase uses are not declared and the default value are not set, etc... The shelve extension should be using core utilities only and the necessary bit should be moved from rebase into core. In the meantime, I'm taking a small step to get config registration completed with minimal overhead. The rebase extension is shipped with core so registering its config option within core is not a big issue. This is the last step needed before we can install a warning that enforces all config to be registered.
author Boris Feld <boris.feld@octobus.net>
date Fri, 13 Oct 2017 23:00:31 +0200
parents 46610c851216
children f05a6e015ecc
comparison
equal deleted inserted replaced
34830:60802bba1090 34831:44c4ed4ad032
1083 default=4, 1083 default=4,
1084 ) 1084 )
1085 coreconfigitem('worker', 'numcpus', 1085 coreconfigitem('worker', 'numcpus',
1086 default=None, 1086 default=None,
1087 ) 1087 )
1088
1089 # Rebase related configuration moved to core because other extension are doing
1090 # strange things. For example, shelve import the extensions to reuse some bit
1091 # without formally loading it.
1092 coreconfigitem('commands', 'rebase.requiredest',
1093 default=False,
1094 )
1095 coreconfigitem('experimental', 'rebaseskipobsolete',
1096 default=True,
1097 )
1098 coreconfigitem('rebase', 'singletransaction',
1099 default=False,
1100 )