git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: <git@vger.kernel.org>
Cc: "Johannes Schindelin" <johannes.schindelin@gmx.de>,
	"Jeff King" <peff@peff.net>, "Carlos Martín Nieto" <cmn@elego.de>,
	"Thomas Rast" <trast@inf.ethz.ch>
Subject: [PATCH 1/3] t/README: --valgrind already implies -v
Date: Sun, 31 Mar 2013 10:00:15 +0200	[thread overview]
Message-ID: <b8b1ac77b7b81a37ff2918b5d9ec1dae8e364ee1.1364716452.git.trast@inf.ethz.ch> (raw)
In-Reply-To: <cover.1364716452.git.trast@inf.ethz.ch>

From: Thomas Rast <trast@inf.ethz.ch>

This was missed in 3da9365 (Tests: let --valgrind imply --verbose and
--tee, 2009-02-04).

Signed-off-by: Thomas Rast <trast@inf.ethz.ch>
---
 t/README | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/t/README b/t/README
index e4128e5..bc7253c5 100644
--- a/t/README
+++ b/t/README
@@ -95,8 +95,7 @@ appropriately before running "make".
 --valgrind::
 	Execute all Git binaries with valgrind and exit with status
 	126 on errors (just like regular tests, this will only stop
-	the test script when running under -i).  Valgrind errors
-	go to stderr, so you might want to pass the -v option, too.
+	the test script when running under -i).
 
 	Since it makes no sense to run the tests with --valgrind and
 	not see any output, this option implies --verbose.  For
-- 
1.8.2.467.gedf93a5

  reply	other threads:[~2013-03-31  8:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-31  8:00 [PATCH 0/3] tests: --valgrind=tool Thomas Rast
2013-03-31  8:00 ` Thomas Rast [this message]
2013-03-31  8:00 ` [PATCH 2/3] tests: parameterize --valgrind option Thomas Rast
2013-03-31  8:00 ` [PATCH 3/3] tests --valgrind: provide a mode without --track-origins Thomas Rast
2013-03-31  8:37 ` [PATCH 3/4] tests: notice valgrind error in test_must_fail Thomas Rast
2013-04-01 14:27 ` [PATCH 0/3] tests: --valgrind=tool Johannes Schindelin

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=b8b1ac77b7b81a37ff2918b5d9ec1dae8e364ee1.1364716452.git.trast@inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=peff@peff.net \
    --cc=trast@inf.ethz.ch \
    /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).