Obsolescence support in viewer (was: Quick Obsolescence Status)

Pierre-Yves David pierre-yves.david at ens-lyon.org
Sun Sep 23 17:47:58 CDT 2012

On 20 sept. 2012, at 11:47, Angel Ezquerra wrote:

> On Sep 19, 2012 6:36 PM, "Pierre-Yves David" <pierre-yves.david at logilab.fr>
> wrote:
> Also, you seem to plan to have Mercurial 2.4 be the first mercurial version
> with built in support for the obsolete concept.  What do you think would be
> the minimum amount of changes necessary to add some usable obsolete
> support to the next version of TortoiseHg as well?

(FYI 2.3 already have some builtin support for obsolescence, (but far less))

The minimal amount of changes is pretty cheap:

1) Hidden changeset must be hidden. In 2.4 it should be much cheaper by the magic of changelog level filtering. Having some button to show hidden changeset is a bonus

For a better experience you also should implements

2) highlight obsolete and troubled changeset

   In hgview, we have obsolete changeset grayed out and troubled one "orange"
   (as in http://hg-lab.logilab.org/doc/mutable-history/html/_images/hgview-example.png )	

3) show relations between precursors and successors. It's harder but very useful
   (as in http://hg-lab.logilab.org/doc/mutable-history/html/_images/hgview-example.png )

Pierre-Yves David

More information about the Mercurial-devel mailing list