From: DJ Delorie <dj@delorie.com>
To: neroden@doctormoo.dyndns.org
Cc: gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: PROPOSAL: remove utils/msdos from cvs
Date: Wed, 15 May 2002 10:23:00 -0000 [thread overview]
Message-ID: <200205151723.g4FHNpB27772@envy.delorie.com> (raw)
In-Reply-To: <20020515171956.GA4656@doctormoo.dyndns.org> (message from Nathanael Nerode on Wed, 15 May 2002 13:19:56 -0400)
> * utils/msdos is totally obselete.
> * it is never built by anything in the tree.
> * it contains, of all things, binaries.
>
> I propose that all the files in it and its subdirectories be removed
> from CVS.
I've proposed that myself many times ;) I think it's scheduled for
deletion when the 29k targets are removed from gdb.
Most of the sources for those hard-to-build binaries are in
utils/amd-udi/
next prev parent reply other threads:[~2002-05-15 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 10:20 Nathanael Nerode
2002-05-15 10:23 ` DJ Delorie [this message]
2002-05-15 10:34 ` Andrew Cagney
2002-05-15 10:48 ` DJ Delorie
2002-05-15 10:57 ` Andrew Cagney
2002-05-17 3:00 ` Nick Clifton
2002-05-17 7:24 ` DJ Delorie
2002-05-28 3:31 ` Nick Clifton
2002-05-17 2:59 ` Nick Clifton
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=200205151723.g4FHNpB27772@envy.delorie.com \
--to=dj@delorie.com \
--cc=binutils@sources.redhat.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