[RFC] naming of obsolescence troubles

Danek Duvall danek.duvall at oracle.com
Thu Sep 27 10:27:46 CDT 2012


Pierre-Yves David wrote:

> 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.

The other two are adjectives, but you chose a noun here.  Why not the
adjective you already have in the description -- "rewritten"?  Because it
might encompass rewriters of non-immutable changesets?  You could use words
that imply hiding; perhaps a "covering" changeset?

Danek


More information about the Mercurial-devel mailing list