From: Steve Ellcey <sje@cup.hp.com>
To: overseers@sourceware.org
Cc: binutils@sourceware.org, gdb@sourceware.org, insight@sourceware.org
Subject: obsolete directories in src tree: mmalloc, iwidgets, blt
Date: Tue, 04 Apr 2006 22:27:00 -0000 [thread overview]
Message-ID: <200604042227.PAA01781@hpsje.cup.hp.com> (raw)
Overseers,
While looking through the source tree for uses of old (pre 2.5) autoconf
I have found 3 directories that appear to no longer be used; mmalloc,
iwidgets, and blt. I was wondering if we should delete these
directories.
I checked with the insight list (see
http://sources.redhat.com/ml/insight/2006-q1/msg00111.html) about blt
and iwidgets and they seem to be ameniable to removing blt and iwidgets.
blt was never used by insight. iwidgets might have been used, but if it
was it was five or so years ago. I looked at some of the files under
both blt and iwidgets and there are no insight or gdb tags on any of the
files.
My understanding is that mmalloc is also no longer used but it does have
a lot of gdb tags on the files and it has been in use more recently. At
the top level ChangeLog I find:
2005-02-08 Andrew Cagney <cagney@gnu.org>
* MAINTAINERS: Delete reference to dejagnu/ and mmalloc/ from the
gdb/ section. Update GDB's URL.
So I think that is when mmalloc stopped being used. The dejagnu
directory seems to have already been removed but the mmalloc directory
is still there.
So, should these three directories (blt, iwidgets, mmalloc) be deleted?
My main interest is to be able to tell the GCC list that we can update
libtool because everything in the GCC and src trees is now using
autoconf 2.5 or later. So if we want to leave these directories alone,
with the knowledge that they are no longer used, that would probably be
good enough for my purposes. But if they are no longer used, maybe we
should just remove them.
Steve Ellcey
sje@cup.hp.com
next reply other threads:[~2006-04-04 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 22:27 Steve Ellcey [this message]
2006-04-05 0:38 ` Ben Elliston
2006-04-05 17:44 ` Steve Ellcey
2006-04-05 8:04 ` Nick Clifton
2006-04-05 17:48 ` 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=200604042227.PAA01781@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=insight@sourceware.org \
--cc=overseers@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