StatesPlan - a draft of the sprint discussion about liquid hg

[Eric Eisner]

Maybe this is what you meant by 'changeset management', but is does this
proposed semantics do anything for users who don't know about it? Do common
operations intelligently change states?

For example, does it allow you to rebase changesets you just committed, but
forbid you to rebase changesets you just pulled?

On Sat, May 7, 2011 at 16:06, Matt Mackall <mpm at selenic.com> wrote:

> I've written this up in a form I hope gives a pretty clear plan for the
> groundwork here:
>
> http://mercurial.selenic.com/wiki/StatesPlan
>
> This also proposes some UI for this feature (the hg state command and
> the state: field in the log), which we'd been mostly handwaving to this
> point.
>
> I think some people at the sprint missed the discussion of the local
> feature, so please take a look at that.
>
> I've mostly left out Pierre-Yves very interesting model for changeset
> management (briefly discussed at the end) as it would double the length
> of the document to go into a similar level of detail and states need to
> be implemented first at any rate.
>
> Similarly, Henrik and Martin's work on dead heads shows up here as
> 'abandoned heads' mostly to illustrate that it's an orthogonal feature.
>
> --
> Mathematics is the supreme nostalgia of our time.
>
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20110507/cacd3673/attachment.htm>