From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, carlton@kealia.com
Cc: dejagnu@gnu.org, fnasser@redhat.com, gdb@sources.redhat.com
Subject: Re: Print KFAIL's in dejagnu summary?
Date: Mon, 29 Sep 2003 20:05:00 -0000 [thread overview]
Message-ID: <200309291917.h8TJHLhn010447@duracef.shout.net> (raw)
dc> What would make more of a difference for me (and,
dc> presumably, for other people) would be to make it as easy as possible
dc> to compare sum files: regularize the thread output a bit more, get rid
dc> of gratuitous numbers (especially the value of $fp in pc-fp.exp).
I'm all for that.
Michael C
next reply other threads:[~2003-09-29 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 20:05 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-03 15:57 Michael Elizabeth Chastain
2003-10-03 16:06 ` Rob Savoye
2003-10-03 23:28 ` Ben Elliston
2003-09-25 22:13 Michael Elizabeth Chastain
2003-09-25 21:56 Andrew Cagney
2003-09-26 0:03 ` David Carlton
2003-09-27 15:46 ` Andrew Cagney
2003-09-29 19:46 ` David Carlton
2003-09-27 10:34 ` Jim Blandy
2003-10-03 15:52 ` Rob Savoye
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=200309291917.h8TJHLhn010447@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=dejagnu@gnu.org \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.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