Description
Mercurial changeset history can be evolved more flexibly while developers refine, rebase, and exchange draft work.
It is useful for teams using Mercurial workflows that need safer history editing concepts than ad hoc patch movement. History evolution can confuse collaborators if used without shared conventions, so repository policy and backup references matter.