Mercurial 2.3 obsolescence markers: a mixed-client compatibility decision
Compatibility decision A shared repository is being considered for history rewriting with Mercurial’s optional evolve extension. The goal is to choose an obsolescence policy that does not silently lose rewrite metadata when clones run different Mercurial releases. Mercurial 2.3 introduced persistent obsolescence markers. Clients older than that boundary may
mercurial