From: Anthony Green <green@moxielogic.com>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: libffi maintenance
Date: Mon, 02 May 2016 13:51:00 -0000 [thread overview]
Message-ID: <CACxje5_N-oPFqCyX-JpOK+W1MwnP98p9ixh+HJyDG=HdaTqnrA@mail.gmail.com> (raw)
Here's a quick update on libffi maintenance going forward.
I've moved the libffi repo to a new 'project' on github. The bits are
now located at https://github.com/libffi.
In addition, I've granted write permission to three trusted and active
hackers: Tom Tromey, Richard Henderson and Josh Triplett. I plan on
spending a little more time on libffi soon, but there's been a log jam
of PRs over the past year, and I hope this change will help move
things along.
We're also long overdue for a new release. I'd like to assess the
patch backlog in about a month before deciding what to do.
Thanks!
AG
next reply other threads:[~2016-05-02 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 13:51 Anthony Green [this message]
2016-05-03 7:41 ` Andrew Haley
2016-05-03 7:50 ` Jakub Jelinek
2016-05-03 14:39 ` Richard Henderson
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='CACxje5_N-oPFqCyX-JpOK+W1MwnP98p9ixh+HJyDG=HdaTqnrA@mail.gmail.com' \
--to=green@moxielogic.com \
--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).