From: Janis Johnson <janis187@us.ibm.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Janis Johnson <janis187@us.ibm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH/RFC] gut Interoperation section of trouble.texi
Date: Wed, 06 Nov 2002 15:21:00 -0000 [thread overview]
Message-ID: <20021106152237.A3213@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0210311038040.4984-100000@kern.srcf.societies.cam.ac.uk>; from jsm28@cam.ac.uk on Thu, Oct 31, 2002 at 10:43:08AM +0000
On Thu, Oct 31, 2002 at 10:43:08AM +0000, Joseph S. Myers wrote:
> On Wed, 30 Oct 2002, Janis Johnson wrote:
>
> > Most of the information in the Trouble/Interoperation section of the GCC
> > manual is very old, and I suspect that much of it is no longer relevant.
> > I propose that we remove everything that was there in egcs 1.1.2 unless
> > someone comes forward soon to say a particular item still needs to be
> > there.
>
> I propose the more conservative fix of removing everything relating only
> to systems for which support has been removed, or to obsolete versions of
> other GNU tools. I don't think Zack did this when removing support for
> those systems.
I plan to do this but haven't gotten around to it yet. I'd like to
change the format to make it easier to identify which platforms are
being described; do you have suggestions for that, Joseph? Would it
be OK to use nested lists?
Is there a complete list of obsolete targets somewhere?
Janis
prev parent reply other threads:[~2002-11-06 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 16:35 Janis Johnson
2002-10-30 16:44 ` Andrew Pinski
2002-10-31 2:43 ` Joseph S. Myers
2002-11-06 15:21 ` Janis Johnson [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=20021106152237.A3213@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).