From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] libevent: add host variant
Date: Mon, 14 Oct 2013 13:52:11 -0300 [thread overview]
Message-ID: <525C213B.1080707@zacarias.com.ar> (raw)
In-Reply-To: <20131014184524.08e82914@skate>
On 10/14/2013 01:45 PM, Thomas Petazzoni wrote:
>> Apache thrift, upcoming package, same as host-boost.
>
> Then please say so, or include such packages in the patch series.
> Otherwise, there's no way for us, mere reviewers, to know what's coming
> next in your patch queue.
That's because i wanted to send the boost bump breakage fix and it was
on top of what i've already had done to boost.
Thrift needs some more testing and i didn't want to hold the fix back
(and also a filename collision fix with python-thrift because someone
thought it was wise to use the same naming convention for tarballs as
the upstream project for a subset of said thing).
Regards.
prev parent reply other threads:[~2013-10-14 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 14:15 [Buildroot] [PATCH 1/3] libevent: add host variant Gustavo Zacarias
2013-10-14 14:15 ` [Buildroot] [PATCH 2/3] boost: " Gustavo Zacarias
2013-10-14 16:39 ` Thomas Petazzoni
2013-10-14 14:15 ` [Buildroot] [PATCH 3/3] boost: fix build failures after version bump Gustavo Zacarias
2013-10-14 20:26 ` Luca Ceresoli
2013-10-14 20:49 ` Peter Korsgaard
2013-10-14 16:39 ` [Buildroot] [PATCH 1/3] libevent: add host variant Thomas Petazzoni
2013-10-14 16:40 ` Gustavo Zacarias
2013-10-14 16:45 ` Thomas Petazzoni
2013-10-14 16:52 ` Gustavo Zacarias [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=525C213B.1080707@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.