Obsolete Markers and Phases

[Pierre-Yves David]

On Thu, Aug 02, 2012 at 09:06:02AM -0700, v wrote:
> 
> Pierre-Yves David wrote
> > 
> > Let me reverse your question:
> > 
> >     What purpose public phase would serve if public changeset where
> > mutable?
> > 
> 
> The changeset itself remains unchanged. An obsolete maker tells you that it
> has been succeeded by a newer changeset.

You can create obsolescence marker pointing to public changeset -can- be created. But the public changeset will not become obsolete. And the successors will be tagged an error case: "latecomer"

See http://hg-lab.logilab.org/doc/mutable-history/html/obs-terms.html for details

> This is analogous to the changesets themselves recording changes to
> "published" files. The state of the file at changeset n never changes, but
> changeset n+1 records a subsequent change.

This is already the implementation of the whole obsolescence business.

-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20120802/89b28a73/attachment.asc>