From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2015.08 release goals
Date: Mon, 4 May 2015 16:48:41 +0200 [thread overview]
Message-ID: <20150504164841.40856c60@free-electrons.com> (raw)
In-Reply-To: <CAMQcK5+DtuXQRSx4W7GhbpxBxy12H9f1PNYGMLuFpyCbTm4RGQ@mail.gmail.com>
Ryan,
On Mon, 4 May 2015 09:45:59 -0500, Ryan Barnett wrote:
> > Have you been able to work with upstream about the Python stuff?
>
> We no longer are doing the "Python stuff" in the audit package - which
> is what you are referring to here.
Yes, exactly. So what was the solution to overcome the
cross-compilation issue of the upstream audit logic?
>
> > Also, I think if you want to get things merged in 2015.08, it would be
> > good to increase the frequency of the patch submissions to take into
> > account review comments and so on. If you wait several months between
> > each iteration, then it's going to take ages because reviewers are
> > losing/forgetting the context and you kind of start over again from
> > scratch each time.
>
> Correct - we will make sure that we respond in a much more timely
> manner since this has become a priority for us.
Excellent. I will also try to dedicate some time to reviewing/testing
your submissions, since I did that in the past for the SELinux stuff.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-04 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 9:53 [Buildroot] 2015.08 release goals Thomas Petazzoni
2015-05-04 14:20 ` Ryan Barnett
2015-05-04 14:30 ` Thomas Petazzoni
2015-05-04 14:45 ` Ryan Barnett
2015-05-04 14:48 ` Thomas Petazzoni [this message]
2015-05-04 15:05 ` Ryan Barnett
2015-05-04 16:38 ` Arnout Vandecappelle
2015-05-04 16:42 ` Thomas Petazzoni
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=20150504164841.40856c60@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 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.