From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com
Subject: bogged down in sunday testing
Date: Mon, 24 Mar 2003 05:22:00 -0000 [thread overview]
Message-ID: <200303240521.h2O5Lxu01166@duracef.shout.net> (raw)
Okay, I capitulate. My last Sunday report was 2003-02-28. I am
bogged down and I could use a little help from my friends.
The problem is that I have multiple systemic failures with gcc HEAD.
I've reported one of them as pr gcc/10055, but there are several more.
I'm thinking of just dropping coverage of gcc HEAD for a while so that
I can make reports oriented towards getting gdb 5.4/6.0 released.
I don't think that 'works with gcc HEAD' is a release criterion.
I can drop coverage, treat the gcc HEAD bugs as a separate task,
and get back in gear, like testing that java regression
fix from David Carlton.
Does that sound reasonable?
Michael C
next reply other threads:[~2003-03-24 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 5:22 Michael Elizabeth Chastain [this message]
2003-03-24 15:32 ` Daniel Jacobowitz
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=200303240521.h2O5Lxu01166@duracef.shout.net \
--to=mec@shout.net \
--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