All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Major patch sets to review and test
Date: Sat, 29 Mar 2014 10:40:45 +0100	[thread overview]
Message-ID: <20140329104045.13985ff3@skate> (raw)

Hello,

As you've noticed, I've started committing a few patches. Peter is on
business trip for a week, so I'm temporarily taking over the
maintenance of Buildroot, with Peter's agreement of course.

I'd like to take advantage of this to make some progress on at least a
few of the major patch series that are sitting in patchwork, and
therefore I would like people to comment/test/review those patch series.

The patch series I would like to have a look at are:

 * The Python 2 / Python 3 fixes from Samuel. This series is
   particularly important because it's needed to fix a number of
   recurrent autobuilder failures. I'd especially appreciate to get some
   reviews from Arnout on this series.

   http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/79108/

 * The virtual package infrastructure from Yann.

   http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/79441/

 * The download infrastructure changes from Yann.

   http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/79474/

Of course, reviews on other patches are also appreciated, but I'd like
to put the emphasis on those three series. I know they are not the
easiest ones, but we need to get through them.

Thanks!

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

                 reply	other threads:[~2014-03-29  9:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140329104045.13985ff3@skate \
    --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 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.