Neal Becker writes: > I see only 'draft' or 'secret' phase changesets can be evolved. Why is this > restriction necessary?
This is necessary to keep source control easy (what’s published should not change; when you rewrite a public changeset you cannot know if someone already pulled it), to make it possible to remove rewritten changesets at some point (when the new changeset becomes public, the draft changesets are no longer necessary) and to keep the behaviour stable when coming from old Mercurial to current Mercurial. > Can I retroactively change phase of previous changesets to draft if needed? Yes, though that needs the --force option. However with modern Mercurial the default phase is draft, so if the phase is public that’s a pretty good indicator that rewriting the changeset isn’t a good idea because you already pushed it. Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken
signature.asc
Description: PGP signature
_______________________________________________ Mercurial mailing list [email protected] https://www.mercurial-scm.org/mailman/listinfo/mercurial
