From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: why do we set prms_id/bug_id in GDB testcases?
Date: Mon, 26 Apr 2010 22:11:00 -0000 [thread overview]
Message-ID: <20100426221106.GA2951@adacore.com> (raw)
In-Reply-To: <4BD5E4D2.6020702@codesourcery.com>
> In fact I would go further, and say that *anything* in the GDB
> testsuite without a known use should be deleted. The unfinished
> bits routinely soak up our time puzzling over what they are supposed
> to be for. If someone has a use for some bit, then it's up to them
> to document in the testsuite somewhere.
Sounds like a plan to me, I definitely agree on the amount of time
they tend to soak up. I'll let things sit for a week or two, and
start looking at whacking them all. Maybe I can add a command such
as PR gdb/#### in the few cases where we do provide a number. It's
going to be a little painful, because of course the numbers are
probably from the old database, so I'd have to check each of them.
But there aren't too many, fortunately.
--
Joel
next prev parent reply other threads:[~2010-04-26 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 17:01 Joel Brobecker
2010-04-26 19:00 ` Tom Tromey
2010-04-26 19:09 ` Stan Shebs
2010-04-26 22:11 ` Joel Brobecker [this message]
2010-05-05 18:14 ` Joel Brobecker
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=20100426221106.GA2951@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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