From: Matthias Klose <doko@ubuntu.com>
To: gcc Development <gcc@gcc.gnu.org>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>,
Ian Lance Taylor <iant@golang.org>
Subject: libffi maintenance within GCC?
Date: Thu, 27 Oct 2016 12:56:00 -0000 [thread overview]
Message-ID: <48a433ca-9f6d-3b5b-9485-64261d812b66@ubuntu.com> (raw)
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?
Matthias
next reply other threads:[~2016-10-27 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 12:56 Matthias Klose [this message]
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
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=48a433ca-9f6d-3b5b-9485-64261d812b66@ubuntu.com \
--to=doko@ubuntu.com \
--cc=gcc@gcc.gnu.org \
--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).