From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git
Date: Fri, 07 Aug 2015 11:47:48 -0700 [thread overview]
Message-ID: <xmqq1tffylyj.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150806045535.GA7014@sigill.intra.peff.net> (Jeff King's message of "Thu, 6 Aug 2015 00:55:35 -0400")
Jeff King <peff@peff•net> writes:
> PS I don't recall the outcome of our last discussion on the "verbose"
> test function. Here it makes debug output for the "grep" above more
> readable when it fails. But it also looks weird not to have the
> matching negative one for the final grep (which could be
> test_must_fail in this case, but we do not usually apply that to
> non-git commands). If you would prefer to strip out the "verbose"
> (from here and the test just below) while squashing, I am OK with
> that.
Yeah, let's do that then.
next prev parent reply other threads:[~2015-08-07 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 22:55 What's cooking in git.git Junio C Hamano
2015-08-05 23:14 ` David Turner
2015-08-05 23:58 ` Junio C Hamano
2015-08-07 16:40 ` Junio C Hamano
2015-08-06 4:55 ` Jeff King
2015-08-06 5:29 ` [PATCH 0/2] ./t5512-*.sh -x complaints Jeff King
2015-08-06 5:31 ` [PATCH 1/2] test-lib: turn off "-x" tracing during chain-lint check Jeff King
2015-08-06 5:33 ` [PATCH 2/2] test-lib: disable trace when test is not verbose Jeff King
2015-08-07 18:47 ` Junio C Hamano [this message]
2015-08-06 10:19 ` What's cooking in git.git Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2006-12-13 21:38 Junio C Hamano
2006-01-12 0:04 Junio C Hamano
2006-01-14 3:45 ` Junio C Hamano
2006-01-16 10:53 ` Petr Baudis
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=xmqq1tffylyj.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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