From: Andrew Haley <aph@redhat.com>
To: Matthias Klose <doko@ubuntu.com>,
gcc Development <gcc@gcc.gnu.org>,
Anthony Green <green@redhat.com>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>,
Ian Lance Taylor <iant@golang.org>
Subject: Re: libffi maintenance within GCC?
Date: Thu, 27 Oct 2016 13:59:00 -0000 [thread overview]
Message-ID: <0e3249a8-7446-50c9-67b5-6632c837f4cb@redhat.com> (raw)
In-Reply-To: <48a433ca-9f6d-3b5b-9485-64261d812b66@ubuntu.com>
On 27/10/16 13:55, Matthias Klose wrote:
> With the removal of libgcj, the only user of libffi in GCC is libgo, however
> there is now no maintainer listed anymore for libffi in the MAINTAINERS file,
> and the libffi subdir is a bit outdated compared to the libffi upstream
> repository (got aware of this by libffi issue #197). Who would be responsible
> now to update / review libffi patches, just the global reviewers, or should
> libffi be maintained by the libgo maintainers?
libffi has always been maintained by the appropriate back-end maintainers.
Andrew.
prev parent reply other threads:[~2016-10-27 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 12:56 Matthias Klose
2016-10-27 13:09 ` Anthony Green
2016-10-28 3:03 ` Ian Lance Taylor
2016-10-28 8:17 ` Andrew Haley
2016-10-27 13:59 ` Andrew Haley [this message]
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=0e3249a8-7446-50c9-67b5-6632c837f4cb@redhat.com \
--to=aph@redhat.com \
--cc=doko@ubuntu.com \
--cc=gcc@gcc.gnu.org \
--cc=green@redhat.com \
--cc=iant@golang.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).