Robustness if hgrc is missing
Nowadays, it'd be a major inconsistency for .hg/hgrc
not to exist in a server-side Mercurial repository on Heptapod.
However, as was highlighted by #742 (closed), it can happen in long-standing instances of our early adopters, and we should make at least mv_repository
more robust about that, as it can block the hashed storage migration.
Task list:
-
make mv_repository
create thehgrc
file with default content if missing (perhaps with inheritance set toFalse
in order not to change any behavioural aspect) -
chase down parts in the code base where the existence of the main hgrc
is simply assumed (methods to change configuration, notably) -
backport to Heptapod 0.23