From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien CORJON <corjon.j@ecagroup.com>
Date: Thu, 28 Apr 2016 14:15:05 +0000
Subject: [Buildroot] 2016.05-rc1 approaching: what to merge?
In-Reply-To: <20160428160000.5db9d1cb@free-electrons.com>
References: <20160428160000.5db9d1cb@free-electrons.com>
Message-ID: <57221AE9.2060207@ecagroup.com>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Thomas, All,

Le 28/04/2016 16:00, Thomas Petazzoni a ?crit :
> Hello,
>
> We're approaching the end of April, and therefore the beginning of May,
> which means that 2016.05-rc1 will be released soon, most likely in
> about a week.
>
> As a reminder, once -rc1 is released, we don't merge new packages or
> version bumps, but only build fixes, security fixes, documentation
> updates, etc. Of course, anything that doesn't get merged before -rc1
> can be merged for the next release, 2016.08.
>
> 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 your feedback,
>
> Thomas
>

Regards,

Julien

[1] https://patchwork.ozlabs.org/patch/547683/