On 04/17/2017 04:24 PM, Yuya Nishihara wrote:
On Sun, 16 Apr 2017 02:55:26 +0200, Pierre-Yves David wrote:
# HG changeset patch
# User Pierre-Yves David <pierre-yves.da...@ens-lyon.org>
# Date 1492302771 -7200
# Sun Apr 16 02:32:51 2017 +0200
# Node ID 7ec1415a4de91a5c56e549cd4a40cb8e9411f8d9
# Parent 276dd8ba6084f1463faca2b57914b8fc3c96c776
# EXP-Topic color
# Available At https://www.mercurial-scm.org/repo/users/marmoute/mercurial/
# hg pull
https://www.mercurial-scm.org/repo/users/marmoute/mercurial/ -r 7ec1415a4de9
color: turn on by default (but for windows)
Color support is all in core for a couple of months. I've browsed the bug
tracker
without finding any blocker bug. So I'm moving forward and enable color on by
default before '4.2-rc'. In the worse case, having it on in the release
candidate will help us to find blocker bug and we can turn it off for the final
release.
Seems fine. Queued the series, thanks.
Can you update the help as a followup?
ah, yes. patch coming soon.
hgext/color.py can also be removed
and marked as a builtin, but that isn't important.
I wanted to mimize the possible churn on stable if we have to backout
the change in default during the freeze. My plan is to clan this up
early in the 4.3 cycle if the changes survive in the 4.2 release.
Cheers,
--
Pierre-Yves David
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
