From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/i386] Make codestream deprecated?
Date: Wed, 08 Jan 2003 21:03:00 -0000 [thread overview]
Message-ID: <3E1C9225.8050605@redhat.com> (raw)
In-Reply-To: <20030108203021.GA5740@nevyn.them.org>
> Besides: this is why you should _remove_ them, rather than just
> commenting them, if you want them to go away.
The implication here being that I'm not removing deprecated code?
The simple reality is that it is not possible for a single individual
remove all the old code in a single hit. It takes a group of people
co-operating, and it takes time.
If you look through the change log you'll notice that deprecated methods
are being removed from the core of GDB, but the -tdep and -nat files are
being left largely untouched. Then, every so often, I or another
maintainer will expunge the deprecated code from a target being it back
into synck. Over time the old code moves to the edges of gdb where it
wilters and dies.
Andrew
next prev parent reply other threads:[~2003-01-08 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 16:39 Andrew Cagney
2002-12-01 17:02 ` Daniel Jacobowitz
2002-12-01 17:51 ` Andrew Cagney
2002-12-07 10:16 ` Mark Kettenis
2003-01-08 20:18 ` Andrew Cagney
2003-01-08 20:31 ` Daniel Jacobowitz
2003-01-08 21:03 ` Andrew Cagney [this message]
2003-01-08 21:13 ` Daniel Jacobowitz
2003-01-08 21:19 ` Daniel Jacobowitz
2003-01-08 22:43 ` Andrew Cagney
2003-01-30 3:31 ` Andrew Cagney
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=3E1C9225.8050605@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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