From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [ob] Eliminate another gdb_suppress_entire_file
Date: Fri, 23 Jun 2006 03:40:00 -0000 [thread overview]
Message-ID: <20060623033948.GA3253@nevyn.them.org> (raw)
In-Reply-To: <20060623033531.GJ976@adacore.com>
On Thu, Jun 22, 2006 at 08:35:31PM -0700, Joel Brobecker wrote:
> Oh ho, I just did a quick grep, and found 352 occurences.
> That's a lot of work... I wonder if we could do that in a mechanical
> way. It seems as though replacing this by an error followed by a return
> would be OK, but not ideal.
I've been using untested followed by return. Why wouldn't that be
ideal?
> Hmmm. Perhaps a first step to stop any potential spread would be to
> rename it deprecated_gdb_suppress_entire_file.
Just as much work as changing it, really...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-23 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 19:58 Daniel Jacobowitz
2006-06-23 3:11 ` Joel Brobecker
2006-06-23 3:22 ` Daniel Jacobowitz
2006-06-23 3:35 ` Joel Brobecker
2006-06-23 3:40 ` Daniel Jacobowitz [this message]
2006-06-23 4:04 ` Joel Brobecker
2006-06-23 12:34 ` 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=20060623033948.GA3253@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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