[PATCH] evolution: make troubles appear in default log (issue4686)

Piotr Listkiewicz piotr.listkiewicz at gmail.com
Tue Sep 6 04:35:03 EDT 2016


>
> I think having a way to show troubled changesets as such in the log is a
> good idea, but the best we're able to do here is to add a new built-in
> template (cf. `hg log -T phases`). The default log output is very strongly
> a part of our command-line API, and changing it (even additively!) is a
> no-no.


You are right, im sending V2 which uses template to show troubled changesets

2016-09-02 17:26 GMT+02:00 Kevin Bullock <kbullock+mercurial at ringworld.org>:

> > On Sep 2, 2016, at 04:38, liscju <piotr.listkiewicz at gmail.com> wrote:
> >
> > # HG changeset patch
> > # User liscju <piotr.listkiewicz at gmail.com>
> > # Date 1472809041 -7200
> > #      Fri Sep 02 11:37:21 2016 +0200
> > # Node ID 463b164126a0db3f7147787ace34f74deeccc03f
> > # Parent  f148bfa40489269be2e48046734f81065129847a
> > evolution: make troubles appear in default log (issue4686)
> >
> > This patch is request for comment, it does not update failing
> > test due to new information about troubles, it adds one test
> > to show how troubles looks like in default log.
>
> I think having a way to show troubled changesets as such in the log is a
> good idea, but the best we're able to do here is to add a new built-in
> template (cf. `hg log -T phases`). The default log output is very strongly
> a part of our command-line API, and changing it (even additively!) is a
> no-no.
>
> pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
> Kevin R. Bullock
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160906/3ab526ae/attachment.html>


More information about the Mercurial-devel mailing list