From: Ben Elliston <bje@au1.ibm.com>
To: Bryce McKinlay <bmckinlay@gmail.com>
Cc: Ben Elliston <bje@au1.ibm.com>, GCC Java <java@gcc.gnu.org>
Subject: Re: libjava testsuite nit
Date: Fri, 08 Aug 2008 11:09:00 -0000 [thread overview]
Message-ID: <1218193714.12336.2.camel@helios> (raw)
In-Reply-To: <7230133d0808080025p7edb7a17ree2e0c8efabfca8d@mail.gmail.com>
On Fri, 2008-08-08 at 08:25 +0100, Bryce McKinlay wrote:
> I suppose this was to make it easy to locate the offending test in the
> event of a failure. There might be test cases with similar names in
> different paths. I don't see a problem stripping the path in the pass
> case, though. Maybe just report the full path when a test fails.
Oh, good thinking. Let's try that.
Cheers, Ben
next prev parent reply other threads:[~2008-08-08 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 23:30 Ben Elliston
[not found] ` <7230133d0808080025p7edb7a17ree2e0c8efabfca8d@mail.gmail.com>
2008-08-08 11:09 ` Ben Elliston [this message]
2008-08-08 16:19 ` Tom Tromey
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=1218193714.12336.2.camel@helios \
--to=bje@au1.ibm.com \
--cc=bmckinlay@gmail.com \
--cc=java@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).