From: Tom Tromey <tromey@redhat.com>
To: kaz Kojima <kkojima@rr.iij4u.or.jp>
Cc: gcc-patches@gcc.gnu.org, java@gcc.gnu.org,
joern.rennecke@superh.com, aoliva@redhat.com,
GCC Hackers <gcc@gcc.gnu.org>
Subject: Re: Unreviewed patch
Date: Thu, 12 Jun 2003 14:42:00 -0000 [thread overview]
Message-ID: <87u1av8jrb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200306121332.h5CDWGJ10519@r-rr.iij4u.or.jp>
>>>>> "kaz" == kaz Kojima <kkojima@rr.iij4u.or.jp> writes:
kaz> libffi sh64-*-linux* support:
kaz> <URL:http://gcc.gnu.org/ml/gcc-patches/2003-05/msg02321.html>
As you've discovered, libffi is a bit under maintained. I'm not
really the person to do it -- I'd do little more than rubber stamp
patches that come in. I'm happy to do that, though, in the absence of
a better process. Hopefully some more qualified person out there will
speak up (and we'll end up with a libffi entry in MAINTAINERS).
I believe we've agreed in the past that port maintainers can make
port-specific libffi changes. So I think you can check in your fix on
that basis.
Tom
next parent reply other threads:[~2003-06-12 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200306121332.h5CDWGJ10519@r-rr.iij4u.or.jp>
2003-06-12 14:42 ` Tom Tromey [this message]
2003-06-12 15:22 ` Anthony Green
2003-06-12 16:09 ` Joseph S. Myers
2003-06-12 23:19 ` kaz Kojima
[not found] ` <3EE89AEE.452EC932@superh.com>
2003-06-12 15:47 ` Gerald Pfeifer
2002-07-25 7:34 Momchil Velikov
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=87u1av8jrb.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=joern.rennecke@superh.com \
--cc=kkojima@rr.iij4u.or.jp \
/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).