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] 2015.08 release goals
Date: Mon, 4 May 2015 16:30:10 +0200	[thread overview]
Message-ID: <20150504163010.188f3ef5@free-electrons.com> (raw)
In-Reply-To: <CAMQcK5JYGAkJT0y9VCHdEQiBA8AWaojpSqdKYYD4jHjNUKxvMg@mail.gmail.com>

Ryan,

On Mon, 4 May 2015 09:20:50 -0500, Ryan Barnett wrote:

> We were hoping that our outstanding SE Linux patchset could be
> targeted for merge during this time too.

For 2015.05 it's obviously too late, Peter will probably cut -rc1
either today or in the next few days.

> The patches have seen a lot
> of changes since the last version including a reduction in the number
> of patches. We plan on sending out a v5 towards the end of this month.

Have you been able to work with upstream about the Python stuff?

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.

> I have updated the elinux page linked above with this.

Good!

Thanks a lot for working on this!

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

  reply	other threads:[~2015-05-04 14:30 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 [this message]
2015-05-04 14:45     ` Ryan Barnett
2015-05-04 14:48       ` Thomas Petazzoni
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=20150504163010.188f3ef5@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