From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, jimb@redhat.com
Cc: gdb@sources.redhat.com, mec.gnu@mindspring.com
Subject: Re: Technical criteria for retaining symbol readers
Date: Wed, 23 Jun 2004 19:50:00 -0000 [thread overview]
Message-ID: <20040623195109.E8A974B104@berman.michael-chastain.com> (raw)
jimb> I'd also like to have some kind of requirement for testability.
I would, too. My preference would be that we look at gdb-testers@
and if there are no test results for feature X for the past N years,
that counts against keeping feature X. gcc uses that as one factor
in deciding whether to obsolete stuff.
As far as Andrew's original proposal goes, it's okay with me to
set up some criteria for dropping formats.
Michael C
next reply other threads:[~2004-06-23 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 19:50 Michael Elizabeth Chastain [this message]
2004-06-23 20:14 ` Andrew Cagney
2004-06-28 23:59 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 15:39 Andrew Cagney
2004-06-23 18:44 ` Jim Blandy
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=20040623195109.E8A974B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).