From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: Much of remote-utils obsolete now?
Date: Thu, 09 Jan 2003 19:00:00 -0000 [thread overview]
Message-ID: <20030109190022.GA31708@nevyn.them.org> (raw)
In-Reply-To: <20020904174431.GA9914@nevyn.them.org>
On Wed, Sep 04, 2002 at 01:44:31PM -0400, Daniel Jacobowitz wrote:
> On Wed, Sep 04, 2002 at 01:16:23PM -0400, Andrew Cagney wrote:
> > >On Wed, Sep 04, 2002 at 09:26:09AM -0700, Stan Shebs wrote:
> > >
> > >>Daniel Jacobowitz wrote:
> > >>
> > >
> > >>>remote-utils.[ch] claim to be generic support functions, but except for
> > >>>some
> > >>>stray calls in remote-array.c which could be easily removed, all the
> > >>>references were in the now-obsolete remote-bug.c module. I'd like to see
> > >>>this code die too, especially the undocumented and pretty much useless
> > >>>"remote" command.
> > >>>
> > >
> > >>remote-utils was obsolete several years ago, and I bet not one single
> > >>person has used
> > >>remote-array in five years at least.
> > >
> > >
> > >Well, then :) Andrew, sounds like we have some more obsoletion
> > >candidates.
> >
> > Yep. My obsolete queue has maxed out though (until after 5.3 has been
> > released and I've zapped any of the current stuff).
> >
> > Perhaphs bug report it so that someone remembers to ``accidently
> > deleted'' when the i960 stuff goes in ~2 months.
>
> Check. It's gdb/685.
Hey, Andrew... should we //OBSOLETE or just ``accidentally delete''
these? I'm open for either. That's remote-utils.[ch] and
remote-array.c.
Incidentally, mon960-rom.o can be removed now; nothing left references
it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-01-09 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 14:15 Daniel Jacobowitz
2002-09-04 9:26 ` Stan Shebs
2002-09-04 9:29 ` Daniel Jacobowitz
2002-09-04 10:16 ` Andrew Cagney
2002-09-04 10:44 ` Daniel Jacobowitz
2003-01-09 19:00 ` Daniel Jacobowitz [this message]
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=20030109190022.GA31708@nevyn.them.org \
--to=drow@mvista.com \
--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