[RFC] naming of obsolescence troubles

[Pierre-Yves David]

I'm about to submit patches to compute the two remaining troubles related to
mutable history exchanges[1] (the first is "unstable" already in 2.3). But
their name are not fully hammered yet.
Please read the sentences below and discuss the *terms* used.


    Exchange mutable history can bring different kind of *troubles*.

    First, ancestors of a changeset may becomes obsoletes. Such changeset are
    called *unstable*.

    Second, a changeset may be a rewritten of a changeset now immutable. Such
    changeset are called *latecomer*.

    Third, multiple change may try to rewrite the same changeset. Such
    changeset are called *divergent*.

    A changeset is called *troubled* when it is affected by at least one
    *troubles* (*unstable*, *latecomer* or *divergent*)


I'm not very happy with *latecomer* but nobody came with a better proposal for now.


Cheers


#1 For those who are lost:

    A full sum-up of the concept is avaible here

        http://hg-lab.logilab.org/doc/mutable-history/html/obs-concept.html

    A full sum-up of the naming is available here:

        http://hg-lab.logilab.org/doc/mutable-history/html/obs-terms.html
-- 
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://selenic.com/pipermail/mercurial-devel/attachments/20120927/d160778e/attachment.pgp>