From: Richard Sandiford <rdsandiford@googlemail.com>
To: binutils@sourceware.org
Cc: gcc@gcc.gnu.org, linux-mips@linux-mips.org
Subject: Re: RFC: Adding non-PIC executable support to MIPS
Date: Tue, 01 Jul 2008 23:02:59 +0100 [thread overview]
Message-ID: <87r6ad460c.fsf@firetop.home> (raw)
In-Reply-To: <87zlp149ot.fsf@firetop.home> (Richard Sandiford's message of "Tue\, 01 Jul 2008 21\:43\:30 +0100")
Richard Sandiford <rdsandiford@googlemail.com> writes:
> I've been thinking about that a lot recently, since I heard about
> your implementation. I kind-of guessed it had been agreed with MTI
> beforehand (although I hadn't realised MTI themselves had written
> the specification). Having thought it over, I think it would be best
> if I stand down as a MIPS maintainer and if someone with the appropriate
> commercial connections is appointed instead. I'd recommend any
> combination of yourself, Adam Nemet and David Daney (subject to
> said people being willing, of course).
I realised afterwards that this might be offensive by who it left out.
For the record, it wasn't supposed to be an exclusive list. Other people
have strong claims too. ;)
Richard
next prev parent reply other threads:[~2008-07-01 22:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 17:58 RFC: Adding non-PIC executable support to MIPS Richard Sandiford
2008-06-30 20:59 ` David VomLehn
2008-06-30 21:19 ` Daniel Jacobowitz
2008-06-30 21:28 ` David VomLehn
2008-07-01 20:22 ` Daniel Jacobowitz
2008-07-01 20:43 ` Richard Sandiford
2008-07-01 22:02 ` Richard Sandiford [this message]
2008-07-02 7:00 ` Adam Nemet
2008-07-02 10:13 ` Thiemo Seufer
2008-07-02 12:08 ` Daniel Jacobowitz
2008-07-02 19:55 ` Richard Sandiford
2008-07-02 20:29 ` Daniel Jacobowitz
2008-07-24 16:16 ` Daniel Jacobowitz
2008-07-24 20:17 ` Daniel Jacobowitz
2008-07-24 20:24 ` Richard Sandiford
2008-07-24 20:56 ` Daniel Jacobowitz
2008-07-27 9:10 ` Richard Sandiford
2008-07-27 21:36 ` Mark Mitchell
2008-07-28 19:43 ` Richard Sandiford
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=87r6ad460c.fsf@firetop.home \
--to=rdsandiford@googlemail.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-mips@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.