From: Eric Christopher <echristo@redhat.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: gcc-patches@gcc.gnu.org, linux-mips@oss.sgi.com
Subject: Re: PATCH: Clean up Linux/mips.
Date: 08 Aug 2001 15:19:28 +0100 [thread overview]
Message-ID: <997280370.1290.43.camel@ghostwheel.cygnus.com> (raw)
In-Reply-To: <20010808071716.A26704@lucon.org>
>
> No. I will let their maintainers decide what to do. Personally, I think they
> should use it :-(. But it may require additional changes.
>
*sigh* That'd be me then. Ok. Make sure your changelog entry states
that mipsel*-linux-* is the only one using it then.
Thanks.
-eric
--
Look out behind you!
next prev parent reply other threads:[~2001-08-08 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 15:42 PATCH: Clean up Linux/mips H . J . Lu
2001-08-08 13:51 ` Eric Christopher
2001-08-08 14:17 ` H . J . Lu
2001-08-08 14:19 ` Eric Christopher [this message]
2001-08-08 14:35 ` H . J . Lu
2001-08-08 14:38 ` Eric Christopher
2001-08-08 14:47 ` H . J . Lu
2001-08-08 15:04 ` Mark Mitchell
2001-08-08 15:08 ` H . J . Lu
2001-08-08 15:39 ` Mark Mitchell
2001-08-08 15:45 ` H . J . Lu
2001-08-08 15:52 ` Mark Mitchell
2001-08-08 16:09 ` H . J . Lu
2001-08-08 16:12 ` Mark Mitchell
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=997280370.1290.43.camel@ghostwheel.cygnus.com \
--to=echristo@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl@lucon.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