Denis Laxalde a écrit :
# HG changeset patch
# User Denis Laxalde <denis.laxa...@logilab.fr>
# Date 1476094018 -7200
# Mon Oct 10 12:06:58 2016 +0200
# Node ID d9f7776c40b8c82bf438322f2442d99c4e116161
# Parent 6c916ce602f5c92c5a5a4de954629670b8c7ca8c
# EXP-Topic evolve-ui
cmdutil: add support for evolution "troubles" display in changeset_printer
Add a "troubles" line in changeset header along with a couple of labels on
"log.changeset" line to indicate whether a changeset is troubled or not and
which kind trouble occurs.
I did this during the sprint and then realized that there has been some
earlier and similar proposals. For the record:
*
https://www.mercurial-scm.org/pipermail/mercurial-devel/2016-September/087850.html
(evolution: make troubles appear in default log)
*
https://www.mercurial-scm.org/pipermail/mercurial-devel/2016-September/087924.html
(evolve: add template to show evolution troubles) (concerns the evolve
extension)
In replies to the first one,
https://www.mercurial-scm.org/pipermail/mercurial-devel/2016-September/088025.html
seems to imply that such changes adding new information bits to log (and
maybe summary) are acceptable.
--
Denis Laxalde
Logilab http://www.logilab.fr
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
