From: Stan Shebs <shebs@apple.com>
To: Nathanael Nerode <neroden@doctormoo.dyndns.org>
Cc: gdb@sources.redhat.com
Subject: Re: autoconfiscating top level directory -- info wanted
Date: Sun, 27 Jan 2002 19:50:00 -0000 [thread overview]
Message-ID: <3C54CAC3.FE3D0CA2@apple.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0201251656400.19571-100000@nerodeguest>
[Redirecting to GDB list]
Nathanael Nerode wrote:
>
> My next patch is to autoconfiscate the remainder of the 'utils'
> directory. It *looks* like this is part of GDB, and so should be
> submitted to gdb-patches -- is this correct?
Yep, but before you spend too much on it, you should be aware
that the a29k has just been obsoleted, which means that the
code in utils/amd-udi and utils/msdos is obsolete too. The
programs in utils/sparclite are quite likely obsolete also,
check Fujitsu's website to see if they even still make the
boards in question. Even utils/wince is on the chopping block,
again because the support has been abandoned.
That leaves spu, which is my code and which I've been
considering making into a "real" GNU program that sits alongside
the other programs. Autoconfiscation of it would be worthwhile
and much appreciated.
Stan
next parent reply other threads:[~2002-01-28 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0201251656400.19571-100000@nerodeguest>
2002-01-27 19:50 ` Stan Shebs [this message]
2002-01-28 13:25 ` Nathanael Nerode
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=3C54CAC3.FE3D0CA2@apple.com \
--to=shebs@apple.com \
--cc=gdb@sources.redhat.com \
--cc=neroden@doctormoo.dyndns.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