From: "H . J . Lu" <hjl@lucon.org>
To: gcc-patches@gcc.gnu.org
Cc: linux-mips@oss.sgi.com
Subject: Re: A patch for linux/mips libgcc
Date: Wed, 6 Jun 2001 17:45:20 -0700 [thread overview]
Message-ID: <20010606174520.A31252@lucon.org> (raw)
In-Reply-To: <20010606145534.A28021@lucon.org>; from hjl@lucon.org on Wed, Jun 06, 2001 at 02:55:34PM -0700
On Wed, Jun 06, 2001 at 02:55:34PM -0700, H . J . Lu wrote:
> This patch is against gcc 2.86-85. But it is trivial to convert it for
^^^^^^^^^^^^
I meant to say gcc 2.96-85 from RedHat rawhide.
H.J.
prev parent reply other threads:[~2001-06-07 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 21:55 A patch for linux/mips libgcc H . J . Lu
2001-06-07 0:45 ` H . J . Lu [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=20010606174520.A31252@lucon.org \
--to=hjl@lucon.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=linux-mips@oss.sgi.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