From: Daniel Jacobowitz <drow@mvista.com>
To: Jason R Thorpe <thorpej@wasabisystems.com>,
cgd@broadcom.com, binutils@sources.redhat.com
Subject: Re: [PATCH/RFA] MIPS breakage with MDMX changes
Date: Thu, 06 Jun 2002 14:48:00 -0000 [thread overview]
Message-ID: <20020606214425.GA15615@nevyn.them.org> (raw)
In-Reply-To: <20020606144431.G11012@dr-evil.shagadelic.org>
On Thu, Jun 06, 2002 at 02:44:31PM -0700, Jason R Thorpe wrote:
> Hi Chris...
>
> I'm seeing some new testsuite failures for gcc when used with a freshly
> CVS update'd binutils ... The failure mode I'm seeing is:
I checked in a fix for this earlier today - and apparently Thiemo
posted one last week without being noisy about it. We've got you
covered :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-06-06 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 14:44 Jason R Thorpe
2002-06-06 14:48 ` Daniel Jacobowitz [this message]
2002-06-06 14:56 ` Jason R Thorpe
2002-06-06 16:55 ` cgd
2002-06-06 17:03 ` Jason R Thorpe
2002-06-06 17:04 ` cgd
2002-06-06 17:05 ` Daniel Jacobowitz
2002-06-06 17:32 ` Jason R Thorpe
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=20020606214425.GA15615@nevyn.them.org \
--to=drow@mvista.com \
--cc=binutils@sources.redhat.com \
--cc=cgd@broadcom.com \
--cc=thorpej@wasabisystems.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).