public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Anthony Green <green@moxielogic.com>
Cc: Ian Lance Taylor <iant@google.com>, Andrew Haley <aph@redhat.com>,
	 Tom Tromey <tromey@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	 GCJ-patches <java-patches@gcc.gnu.org>,
	"libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: [ping] Re: [patch] [libffi] do not install libffi library, headers and documentation
Date: Sat, 30 Mar 2013 11:26:00 -0000	[thread overview]
Message-ID: <5156CBE5.2090608@ubuntu.com> (raw)
In-Reply-To: <CACxje5-cFFT+7ho=fBdRaxjNzYLe-aoW9NU6X3NT0P8QyPQT6w@mail.gmail.com>

Am 26.03.2013 21:48, schrieb Anthony Green:
> For what it's worth, this patch is fine by me.  I had originally
> proposed that GCC not install these bits.

now applied on trunk and the 4.8 branch.

> As far as maintainers go, I thought that I was once listed in the
> MAINTAINERS file.  Feel free to add Andrew Haley and/or myself.

I didn't hear back form Andrew.  Could you do this yourself, maybe updating
libffi on trunk to the 3.0.13 release? ;)

  Matthias

      reply	other threads:[~2013-03-30 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 12:30 Matthias Klose
2013-02-12 12:44 ` Richard Biener
2013-02-12 12:46   ` Richard Biener
2013-02-18 17:03     ` Matthias Klose
2013-02-19  9:13       ` Richard Biener
2013-03-26 20:04         ` [ping] " Matthias Klose
2013-03-26 20:28           ` Ian Lance Taylor
2013-03-26 20:48             ` Anthony Green
2013-03-30 11:26               ` Matthias Klose [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=5156CBE5.2090608@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=green@moxielogic.com \
    --cc=iant@google.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=libffi-discuss@sourceware.org \
    --cc=tromey@redhat.com \
    /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).