From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: sunshine@sunshineco.com, jrn@google.com, git@vger.kernel.org
Subject: Re: [PATCH v7 0/1] sideband: highlight keywords in remote sideband output
Date: Tue, 07 Aug 2018 14:01:43 -0700 [thread overview]
Message-ID: <xmqqva8lki14.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180807125108.104293-1-hanwen@google.com> (Han-Wen Nienhuys's message of "Tue, 7 Aug 2018 14:51:07 +0200")
Han-Wen Nienhuys <hanwen@google.com> writes:
> Fix nits; remove debug printf.
>
> Han-Wen Nienhuys (1):
> sideband: highlight keywords in remote sideband output
>
> Documentation/config.txt | 12 +++
> help.c | 1 +
> help.h | 1 +
> sideband.c | 125 ++++++++++++++++++++++++++--
> t/t5409-colorize-remote-messages.sh | 87 +++++++++++++++++++
> 5 files changed, 217 insertions(+), 9 deletions(-)
> create mode 100755 t/t5409-colorize-remote-messages.sh
>
> --
> 2.18.0.597.ga71716f1ad-goog
I'll squash in the following while queuing for
<CAPig+cScb_7s4a_ZSVCsr+nBxAHGHZVMZOtnrOgbhZUi96-VFA@mail.gmail.com>
Thanks for sticking to the topic.
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 33bc1a3def..9a38dd2cbb 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1266,7 +1266,7 @@ color.push.error::
color.remote::
If set, keywords at the start of the line are highlighted. The
keywords are "error", "warning", "hint" and "success", and are
- matched case-insensitively. Maybe set to `always`, `false` (or
+ matched case-insensitively. May be set to `always`, `false` (or
`never`) or `auto` (or `true`). If unset, then the value of
`color.ui` is used (`auto` by default).
next prev parent reply other threads:[~2018-08-07 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 12:51 [PATCH v7 0/1] sideband: highlight keywords in remote sideband output Han-Wen Nienhuys
2018-08-07 12:51 ` [PATCH v7 1/1] " Han-Wen Nienhuys
2018-08-17 18:33 ` Junio C Hamano
2018-08-17 18:44 ` Re* " Junio C Hamano
2018-08-18 6:09 ` Jonathan Nieder
2018-08-18 14:40 ` Junio C Hamano
2018-08-18 16:02 ` Junio C Hamano
2018-08-18 16:16 ` Junio C Hamano
2018-08-18 23:22 ` Jeff King
2018-08-20 14:21 ` Junio C Hamano
2018-08-20 12:21 ` Han-Wen Nienhuys
2018-08-20 12:21 ` Han-Wen Nienhuys
2018-08-20 14:32 ` Junio C Hamano
2018-08-18 6:35 ` Jonathan Nieder
2018-08-18 16:06 ` Junio C Hamano
2018-08-07 21:01 ` Junio C Hamano [this message]
2018-08-08 13:12 ` [PATCH v7 0/1] " Han-Wen Nienhuys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqva8lki14.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.com \
--cc=jrn@google.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).