From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH 1/1] Highlight keywords in remote sideband output.
Date: Tue, 31 Jul 2018 07:59:16 -0700 [thread overview]
Message-ID: <xmqqd0v3e9iz.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAFQ2z_NL+8LVmv+E4osq2+nx+qVE4P80it8vjLUwib=HJ5k4Lg@mail.gmail.com> (Han-Wen Nienhuys's message of "Tue, 31 Jul 2018 13:03:53 +0200")
Han-Wen Nienhuys <hanwen@google.com> writes:
> On Mon, Jul 30, 2018 at 11:39 PM Junio C Hamano <gitster@pobox.com> wrote:
>> > + */
>> > +void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
>>
>> I'll make this "static" to this file while queuing.
>
> Does that mean the patch is in?
It depends on your definition of "is in".
It does not mean there is no need to update it further before it
graduates to 'master' and becomes part of the next release, if that
is what you are asking.
I saw others commented on the patch, showing general interest in the
feature, agreeing to the approach taken and suggesting improvements.
I am *not* going to respond to these comments and make further
changes myself (you hopefully will), but expect that these review
discussions to find a good terminal point that results in your
sending out the "hopefully the final best version" in some time. In
the meantime while I am waiting for that, I'd hold onto the version
posted here and build it with all topics in flight that are waiting
for improvements in a similar way by merging it in the 'pu' branch.
And while doing so, I'll minimally modify this initial version so
that the whole thing at least compiles, by making small tweaks like
making a function that should be static static and getting rid of
decl-after-stmt, etc.
That is what I meant by that line, and nothing more.
Thanks.
next prev parent reply other threads:[~2018-07-31 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 12:33 [PATCH 0/1] Highlight keywords in remote sideband output Han-Wen Nienhuys
2018-07-30 12:33 ` [PATCH 1/1] " Han-Wen Nienhuys
2018-07-30 14:52 ` Duy Nguyen
2018-07-31 1:03 ` brian m. carlson
2018-07-30 21:39 ` Junio C Hamano
2018-07-31 11:03 ` Han-Wen Nienhuys
2018-07-31 14:59 ` Junio C Hamano [this message]
2018-07-31 7:37 ` Ævar Arnfjörð Bjarmason
2018-07-31 15:06 ` Duy Nguyen
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=xmqqd0v3e9iz.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.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).