It's necessary to prevent rewriting public history, which can cause very confusing divergence for teams or anyone who has pulled one of your public changesets.
If you are sure that no one has pulled from you can force the phase back to draft using "hg phase -r <rev> -f -d". See "he help phases" and "he help phase" for more details. On Fri, Nov 18, 2016 at 8:49 AM Neal Becker <[email protected]> wrote: > I see only 'draft' or 'secret' phase changesets can be evolved. Why is > this > restriction necessary? > > Can I retroactively change phase of previous changesets to draft if needed? > > _______________________________________________ > Mercurial mailing list > [email protected] > https://www.mercurial-scm.org/mailman/listinfo/mercurial >
_______________________________________________ Mercurial mailing list [email protected] https://www.mercurial-scm.org/mailman/listinfo/mercurial
