From: Anthony Green <green@moxielogic.com>
To: Samuli Suominen <ssuominen@gentoo.org>
Cc: libffi-discuss@sourceware.org
Subject: Re: libffi.pc from libffi-3.1 after `make install` is broken, new release propably in order
Date: Thu, 12 Jun 2014 10:57:00 -0000 [thread overview]
Message-ID: <87ppiez98i.fsf@moxielogic.com> (raw)
In-Reply-To: <538F32BA.5030605@gentoo.org> (Samuli Suominen's message of "Wed, 04 Jun 2014 17:52:42 +0300")
Samuli Suominen <ssuominen@gentoo.org> writes:
> On 31/05/14 15:55, Anthony Green wrote:
>> Samuli Suominen <ssuominen@gentoo.org> writes:
>>
>>> I think 3.1.1 should be rolled to cover issues of:
>> Thanks Samuli. I agree, and I've prepared almost everything. Could you
>> please submit a patch for the last issue below?
>>
>> Thanks!
>
> This patch seems to work here. Be careful, I tried my best to look
> that it doesn't have any
> unexpected consequences. As in, please test.
I tested it a little and it seems to work here. Committed. Thanks!
AG
prev parent reply other threads:[~2014-06-12 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 10:58 Samuli Suominen
2014-05-31 12:55 ` Anthony Green
2014-06-04 14:55 ` Samuli Suominen
2014-06-12 10:57 ` Anthony Green [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=87ppiez98i.fsf@moxielogic.com \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=ssuominen@gentoo.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).