unobsolete via changing phase to public!?

Dominik Ruf dominikruf at gmail.com
Wed Oct 28 06:11:28 UTC 2015


Matt Mackall <mpm at selenic.com> schrieb am Di., 27. Okt. 2015 22:33:

On Tue, 2015-10-27 at 21:16 +0000, Dominik Ruf wrote:
> Hi,
>
> I started playing with the evolve extension and ran into the
> following.
> The documentation
> http://evolution.experimentalworks.net/doc/user-guide.html#id23 says
> that
> there is no 'unobsolete' command.
> But I noticed that if I change the phase of an obsolete revision to
> public
> it becomes visible again.
> And at least I can't see a difference to an normal revision.
> Is this a valid way to 'unobsolete' a revision or is this a bug and
> should
> actually not be possible?

Alice can mark change X obsolete while Bob, on another machine, makes
the same changeset public. So it's impossible to prevent and thus not a
bug. The only question then is what the result should be. Public means
'permanently visible to the world', which trumps whatever obsolete was
trying to do.

-- 
Mathematics is the supreme nostalgia of our time.


Okay I see.
Maybe it would be a good idea to mention this in the documentation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20151028/c62c5458/attachment-0002.html>


More information about the Evolve-testers mailing list