From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>, jimb@redhat.com
Cc: carlton@kealia.com, fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: Don't include value of expression in pc-fp.exp test name
Date: Wed, 01 Oct 2003 15:31:00 -0000 [thread overview]
Message-ID: <3F7AF34A.4070605@redhat.com> (raw)
In-Reply-To: <200309301749.h8UHnZkE029086@duracef.shout.net>
> Michael Elizabeth Chastain <mec@shout.net> writes:
>
>
>> Yeah! It makes my life easier!
>>
>> You need to add '2003' to the copyright year to the top of pc-fp.exp.
>>
>> Proofread. Tested on my test bed with 10 configurations.
>> All the gdb.sum's come out identical now.
>
>
> Fantastic. I think this deserves mention in NEWS.
As Michael well knows, supplemental information, such as which specific
branch of a test passed or failed can be included in paren in the test
message. Any analysis tools comparing test results needs to accomodate
this convention.
If you really want to remove this specific output, then what ever.
However, please don't start removing the supplemental information willy
nilly. Instead, fix your script.
Andrew
next prev parent reply other threads:[~2003-10-01 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 17:49 Michael Elizabeth Chastain
2003-09-30 22:18 ` Jim Blandy
2003-10-01 15:31 ` Andrew Cagney [this message]
2003-10-01 15:49 ` David Carlton
-- strict thread matches above, loose matches on Subject: below --
2003-10-02 22:43 Michael Elizabeth Chastain
2003-10-01 19:06 Michael Elizabeth Chastain
2003-10-02 21:55 ` Andrew Cagney
2003-10-01 16:44 Michael Elizabeth Chastain
2003-10-01 18:29 ` Andrew Cagney
2003-10-01 19:33 ` David Carlton
2003-10-01 4:12 Michael Elizabeth Chastain
[not found] <200309291917.h8TJHLhn010447@duracef.shout.net>
2003-09-30 6:44 ` Jim Blandy
2003-09-30 15:36 ` David Carlton
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=3F7AF34A.4070605@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec@shout.net \
/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