From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH 4/4] t4300 (rebase): don't unnecessarily set GIT_TRACE
Date: Fri, 10 May 2013 12:16:39 -0700 [thread overview]
Message-ID: <20130510191639.GB3478@elie> (raw)
In-Reply-To: <CALkWK0kZWrY5_B3mxuVV1cA-AqvkqJpjRAuSovXLi6OCA+3ybQ@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Can we do better by not printing the -v
> output of the passing tests though?
Not for my use. The output from comprable tests before is often
useful for comparison. I wouldn't be against such an option for
people who want it, though.
Thanks,
Jonathan
next prev parent reply other threads:[~2013-05-10 19:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 14:29 [PATCH 0/4] Trivial cleanups to t3400 (rebase) Ramkumar Ramachandra
2013-05-10 14:29 ` [PATCH 1/4] t3400 (rebase): don't set GIT_AUTHOR_{NAME,EMAIL} Ramkumar Ramachandra
2013-05-10 14:53 ` Eric Sunshine
2013-05-10 14:56 ` Ramkumar Ramachandra
2013-05-10 17:34 ` Junio C Hamano
2013-05-10 14:29 ` [PATCH 2/4] t3400 (rebase): downcase a couple of test titles Ramkumar Ramachandra
2013-05-10 14:29 ` [PATCH 3/4] t3400 (rebase): move lone statement into a test Ramkumar Ramachandra
2013-05-10 14:29 ` [PATCH 4/4] t4300 (rebase): don't unnecessarily set GIT_TRACE Ramkumar Ramachandra
2013-05-10 14:38 ` Junio C Hamano
2013-05-10 14:46 ` Ramkumar Ramachandra
2013-05-10 15:42 ` Junio C Hamano
2013-05-10 16:42 ` Ramkumar Ramachandra
2013-05-10 17:51 ` Junio C Hamano
2013-05-10 18:06 ` Ramkumar Ramachandra
2013-05-10 18:08 ` Ramkumar Ramachandra
2013-05-10 19:07 ` Jonathan Nieder
2013-05-10 19:14 ` Ramkumar Ramachandra
2013-05-10 19:16 ` Jonathan Nieder [this message]
2013-05-10 21:06 ` Junio C Hamano
2013-05-11 11:37 ` Ramkumar Ramachandra
2013-05-13 23:05 ` Jonathan Nieder
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=20130510191639.GB3478@elie \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).