From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] libevent: fix openssl detection when statically linking
Date: Sat, 28 Feb 2015 10:59:31 +0100 [thread overview]
Message-ID: <20150228105931.3bcae77a@free-electrons.com> (raw)
In-Reply-To: <54F0D8A7.9070602@openwide.fr>
Dear Romain Naour,
On Fri, 27 Feb 2015 21:50:47 +0100, Romain Naour wrote:
> > No, I was hoping for Romain to pick up on the task actually :-)
>
> I thought that you would have submit your patch directly on the list.
> Ok sorry, I'll pick up you patch and send it upstream.
Yes, maybe I was not explicit enough. Sorry about this.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-02-28 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 7:54 [Buildroot] [git commit] libevent: fix openssl detection when statically linking Peter Korsgaard
2015-02-27 14:30 ` Thomas Petazzoni
2015-02-27 14:44 ` Peter Korsgaard
2015-02-27 15:01 ` Thomas Petazzoni
2015-02-27 15:15 ` Peter Korsgaard
2015-02-27 20:50 ` Romain Naour
2015-02-28 9:59 ` Thomas Petazzoni [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=20150228105931.3bcae77a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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