Obsolete Markers and Phases

[Pierre-Yves David]

On Thu, Aug 02, 2012 at 08:30:03AM -0700, v wrote:
> 
> Patrick Mézard wrote
> > Phase helps you not mutate changesets which have been published.
> > 
> > 
> > Obsolete helps you describe how non-public changesets have been rewritten.
> > You will not directly use this information but rewriting tools will. The
> > middle of this post has an example of using evolve extension to rewrite a
> > changeset in the middle of a changeset sequence:
> > 
> >   http://selenic.com/pipermail/mercurial-devel/2012-July/042948.html
> > 
> > Note, the "stabilize" call (similar to mq qpush for instance) use 3-way
> > merge instead of patching since the changeset being rewritten is not
> > destroyed but marked obsolete.
> > 
> > Obsolescence markers can also be used in collaborative settings where
> > people work on the same sets of changes. See the end of the post
> > referenced above for more details about this.
> > 
> > Also note, that all this stuff is still experimental :-)
> > 
> 
> What would go wrong if obsolete was used with public changesets?

Let me reverse your question:

    What purpose public phase would serve if public changeset where mutable?

-- 
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/78bd2969/attachment.asc>