From: Jason Molenda <jason-swarelist@molenda.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Zap a29k ultra native stuff
Date: Sat, 01 Dec 2001 21:27:00 -0000 [thread overview]
Message-ID: <20011201212654.A47602@molenda.com> (raw)
Andrew wrote:
>
> The a29k is very much on notice (obsolete announcement sent out).
>
Does this mean you're looking at dropping the utils/amd-udi directory
as well? This is some code to talk to a ROM monitor that was used
on 29k boards long ago, it's a code drop of AMD's own support code
slightly munged to work in our build setup. Mostly, though, it's
1.4MB of wasted disk space on every gdb checkout these days.
Jason
next reply other threads:[~2001-12-02 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 21:27 Jason Molenda [this message]
2001-12-01 22:36 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2001-12-01 14:36 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=20011201212654.A47602@molenda.com \
--to=jason-swarelist@molenda.com \
--cc=gdb-patches@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