From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2016.05-rc1 approaching: what to merge?
Date: Thu, 28 Apr 2016 16:20:40 +0200 [thread overview]
Message-ID: <20160428162040.35a424a9@free-electrons.com> (raw)
In-Reply-To: <CAGm1_ktmOkBg-VoOC2QM+Zn=WKs9ve6YKdc16FctDaohpjz-Sg@mail.gmail.com>
Hello,
On Thu, 28 Apr 2016 16:06:40 +0200, Yegor Yefremov wrote:
> I would like to see Barebox double config feature merged.
On that one, I was waiting for the final review from Arnout. With the
latest changes done by Pieter, I'm happy as it is. I'll merge it over
the WE, hopefully after Arnout gave his Reviewed-by.
> Perhaps Python 3.5 and pyc related stuff.
So Python 3.5 is http://patchwork.ozlabs.org/patch/562627/.
For the .pyc stuff, we have http://patchwork.ozlabs.org/patch/546542/
and http://patchwork.ozlabs.org/patch/580512/. Are you talking about
both of them, or more specifically one of the two?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-28 14:20 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 [this message]
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
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=20160428162040.35a424a9@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