From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: [PATCH] t: send verbose test-helper output to fd 4
Date: Thu, 22 Feb 2018 12:18:44 -0800 [thread overview]
Message-ID: <xmqq371swzff.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180222064836.GA10719@sigill.intra.peff.net> (Jeff King's message of "Thu, 22 Feb 2018 01:48:37 -0500")
Jeff King <peff@peff.net> writes:
> This is a repost of the two patches from:
>
> https://public-inbox.org/git/20180209185710.GA23403@sigill.intra.peff.net/
>
> (now just one patch, since sg/test-i18ngrep graduated and we can do it
> all in one step). The idea got positive feedback, but nobody commented
> on patches and I didn't see them in "What's cooking".
Thanks for clearly explaining the change. Will queue.
next prev parent reply other threads:[~2018-02-22 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 6:48 [PATCH] t: send verbose test-helper output to fd 4 Jeff King
2018-02-22 20:18 ` Junio C Hamano [this message]
2018-02-28 2:30 ` SZEDER Gábor
2018-03-03 6:56 ` Jeff King
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=xmqq371swzff.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=szeder.dev@gmail.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).