From: Johannes Sixt <j.sixt@viscovery.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Windows: Fix intermittent failures of t7701
Date: Wed, 28 Jan 2009 08:26:50 +0100 [thread overview]
Message-ID: <498008BA.2000201@viscovery.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0901271740320.3586@pacific.mpi-cbg.de>
Johannes Schindelin schrieb:
> I use this trick in my valgrind series:
>
> ($PROGRAM; echo $? > exit.code) | $OTHER_PROGRAM &&
> test 0 = "$(cat exit.code)"
Ah, using a file as temporary storage? Why not simply
$PROGRAM > data &&
$OTHER_PROGRAM < data
Hm? ;)
-- Hannes
next prev parent reply other threads:[~2009-01-28 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 13:09 [PATCH] Windows: Fix intermittent failures of t7701 Johannes Sixt
2009-01-27 16:42 ` Johannes Schindelin
2009-01-28 4:28 ` Jeff King
2009-01-28 12:43 ` Johannes Schindelin
2009-01-28 7:26 ` Johannes Sixt [this message]
2009-01-28 8:26 ` Junio C Hamano
2009-01-28 9:52 ` [PATCH v2] " Johannes Sixt
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=498008BA.2000201@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Johannes.Schindelin@gmx.de \
--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).