From: Fred Fish <fnf@specifix.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>,
brobecker@adacore.com,
GDB Patches <gdb-patches@sources.redhat.com>,
Jim Blandy <jimb@codesourcery.com>,
fnf@specifix.com
Subject: Re: [RFA] mips, eabi64, addr_bit == 32
Date: Thu, 08 Jun 2006 19:39:00 -0000 [thread overview]
Message-ID: <200606081540.32318.fnf@specifix.com> (raw)
In-Reply-To: <4488787D.2010601@redhat.com>
On Thursday 08 June 2006 15:20, Michael Snyder wrote:
> Doesn't appear that any resolution ever came out of this.
Correct. I've wanted to find time to go back and try merging Jim's
changes again into a current mainline tree but so far I've been too
busy with other stuff.
Quite a few of the patches merge easily but some are dependent on code
that has since been removed, so will need some work (as I recall).
-Fred
next prev parent reply other threads:[~2006-06-08 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 23:32 Michael Snyder
2006-05-31 23:39 ` Daniel Jacobowitz
2006-05-31 23:47 ` Michael Snyder
2006-06-01 1:55 ` Daniel Jacobowitz
2006-06-08 19:21 ` Michael Snyder
2006-06-08 19:39 ` Fred Fish [this message]
2006-06-17 23:15 ` Mark Kettenis
2006-06-20 20:29 ` Daniel Jacobowitz
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=200606081540.32318.fnf@specifix.com \
--to=fnf@specifix.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.com \
--cc=msnyder@redhat.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