From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andrew Haley <aph@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libffi-discuss@sourceware.org
Subject: Re: Unreviewed libffi patch
Date: Tue, 14 Jun 2011 16:02:00 -0000 [thread overview]
Message-ID: <ydd8vt45rlj.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4DF7806E.3080905@redhat.com> (Andrew Haley's message of "Tue, 14 Jun 2011 16:38:22 +0100")
Andrew Haley <aph@redhat.com> writes:
> On 06/14/2011 04:22 PM, Rainer Orth wrote:
>> The following patch has remained unreviewed for a week:
>
> I think it wasn't cc'd to libffi-discuss@sourceware.org
Right, I hadn't known/had forgotten about that since all my libffi fixes
happen in GCC context. I'd only Cc'ed it to Anthony, but he isn't
listed as libffi maintainer in MAINTAINERS anymore as I just noticed.
>> [libffi] Fix libffi.call/huge_struct.c on Tru64 UNIX
>> http://gcc.gnu.org/ml/gcc-patches/2011-06/msg00644.html
>>
>> It needs a libffi maintainer or global reviewer.
>
> This is OK.
Installed, thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-06-14 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yddpqmg5tgk.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
2011-06-14 15:38 ` Andrew Haley
2011-06-14 16:02 ` Rainer Orth [this message]
[not found] <yddk3mrtk3k.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
2013-05-22 9:58 ` Andrew Haley
[not found] ` <CACxje59X_rLcSd7NO1yUNQEjRjeN9hoNkv+FSbA4MNiKxa9FpQ@mail.gmail.com>
2013-05-22 11:49 ` Rainer Orth
2013-05-22 12:40 ` Jakub Jelinek
2013-05-22 12:45 ` Rainer Orth
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=ydd8vt45rlj.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libffi-discuss@sourceware.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 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).