|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
The reviewboard Mercurial extension makes use of obsolescence markers to enable better handling of history rewriting on review requests. I'd like to add a config setting to the extension to enable obsolescence markers in Mercurial core. This will enable people to produce obsolescence markers with rebase, histedit, etc without having to install evolve (which still isn't advertised as stable even though I've been using it for a year without major problems). Assigning P1 because it is easy and getting people using obsolescence markers is a huge UX win for people who rewrite history.
Created attachment 8512350 [details] MozReview Request: bz://1089935/gps
/r/323 - reviewboard: add a config option to enable obsolescence (bug 1089935) /r/324 - reviewboard: use internal obsolescence activation in test-obsolescence.t /r/325 - reviewboard: use internal obsolescence activation in test-commits-deleted-obsolescence.t /r/326 - reviewboard: use internal obsolescence activation in test-folding-obsolescence.t /r/327 - reviewboard: use internal obsolescence activation in test-multiple-precursors.t /r/328 - reviewboard: remove unused obsolescence activiation from test-push.t Pull down these commits: hg pull review -r 2853d79862052fb0c619f2d8009999ebe08585c9
Pierre-Yves (the man behind obsolescence and changeset evolution) warned me we may not want to do this because it results in a poor user experience in Mercurial (no UI for troubled changeset creation, lack of command to solve trouble, etc). We may want to keep the docs as-is and point them to the evolve extension. Rats.
Wontfixing since the user experience will be bad. Docs reference the mutable-history repository. That's fine.