Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2016.05-rc1 approaching: what to merge?
Date: Sat, 30 Apr 2016 19:05:19 +0200	[thread overview]
Message-ID: <20160430190519.308e4a53@free-electrons.com> (raw)
In-Reply-To: <57221AE9.2060207@ecagroup.com>

Hello,

On Thu, 28 Apr 2016 14:15:05 +0000, Julien CORJON wrote:

> > So the question is: we have ~230 patches pending patchwork. Do you see
> > anything that we should really merge before 2016.05-rc1 is released?  
> 
> I would really appreciate to see android-tools[1] in 2016.05 as I use it 
> for target production which will start in about 2 month.

Thanks for the reminder, I've applied the android-tools patch.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-04-30 17:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 14:00 [Buildroot] 2016.05-rc1 approaching: what to merge? Thomas Petazzoni
2016-04-28 14:06 ` Yegor Yefremov
2016-04-28 14:20   ` Thomas Petazzoni
2016-04-28 14:25     ` Yegor Yefremov
2016-04-30 12:53   ` Thomas Petazzoni
2016-05-01 12:35   ` Thomas Petazzoni
2016-05-01 14:17     ` Yegor Yefremov
2016-05-01 17:10       ` Thomas Petazzoni
2016-04-28 14:15 ` Julien CORJON
2016-04-30 17:05   ` Thomas Petazzoni [this message]
2016-04-28 14:40 ` Gustavo Zacarias
2016-04-30 19:08   ` Thomas Petazzoni
2016-04-28 15:00 ` Bernd Kuhls
2016-04-29 18:12 ` Thomas De Schampheleire
2016-04-29 18:24 ` Carlos Santos

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=20160430190519.308e4a53@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