All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] kernel.bbclass: respect MACHINE_KERNEL_PR
Date: Fri, 21 Oct 2011 14:05:35 +0200	[thread overview]
Message-ID: <3968D33D-7086-4E22-9CA1-9B44BE0DBEBF@dominion.thruhere.net> (raw)
In-Reply-To: <CAP9ODKqFfswQ4Y6fJBJMTjrvnu0syiS3rAWxZjhdtwyx_Z_SWQ@mail.gmail.com>


Op 20 okt. 2011, om 15:02 heeft Otavio Salvador het volgende geschreven:

> On Thu, Oct 20, 2011 at 10:54, Koen Kooi <koen@dominion.thruhere.net> wrote:
> ...
>>> Also, the idea never was to have everyone using bleeding edge for
>>> shipping products. This is what stable releases are for?
>> 
>> That's what stable releases are for, but I don't see a release for OE-core, do you? I see a poky release, but not an OE-core release.
> 
> People, let's calm down.
> 
> I think since Richard disagree about pushing this patch and more then
> one person disagree with Richard, TSC is the way to go.

Executive summary of the TSC meeting:

1) This patch gets applied, but no more PR helpers will be allowed, INC_PR and MACHINE_KERNEL_PR are the only ones tolerated for the time being.
2) kernel.bbclass gets dropped from meta-oe
3) basic-hash will get turned on in master-next
4) super-duper PR automation work will land in master-next and get merged into master when it's deemed "good enough"

The intermediate merge step into master-next is only done if enough people test master-next. If people don't want to test it, the merge and associated breakage will go straight into master.

regards,

Koen


  reply	other threads:[~2011-10-21 12:11 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17 22:18 [PATCH 1/5] kernel.bbclass: blacklist 'perf-dbg' as well for the modules metapackage Dmitry Eremin-Solenikov
2011-09-17 22:18 ` [PATCH 2/5] kernel.bbclass: respect MACHINE_KERNEL_PR Dmitry Eremin-Solenikov
2011-09-17 22:24   ` Otavio Salvador
2011-09-27 13:52   ` Bruce Ashfield
2011-09-27 23:40     ` Koen Kooi
2011-09-28 14:54       ` Richard Purdie
2011-09-28 18:42         ` Koen Kooi
2011-09-28 18:50           ` Dmitry Eremin-Solenikov
2011-09-28 19:50           ` Richard Purdie
2011-09-28 20:04             ` Otavio Salvador
2011-10-20  6:23               ` Koen Kooi
2011-10-20 11:21                 ` Richard Purdie
2011-10-20 11:29                   ` Koen Kooi
2011-10-20 11:35                     ` Otavio Salvador
2011-10-20 11:53                     ` Frans Meulenbroeks
2011-10-20 12:38                     ` Richard Purdie
2011-10-20 12:54                       ` Koen Kooi
2011-10-20 13:02                         ` Otavio Salvador
2011-10-21 12:05                           ` Koen Kooi [this message]
2011-10-20 13:56                         ` Richard Purdie
2011-09-17 22:18 ` [PATCH 3/5] kernel.bbclass: move uImage handling to separate task Dmitry Eremin-Solenikov
2011-09-17 22:25   ` Otavio Salvador
2011-09-21 13:09     ` Dmitry Eremin-Solenikov
2011-09-27 13:39   ` Bruce Ashfield
2011-09-17 22:18 ` [PATCH 4/5] kernel.bbclass: handle .cis firmware Dmitry Eremin-Solenikov
2011-09-27 13:40   ` Bruce Ashfield
2011-09-28 14:50   ` Richard Purdie
2011-09-17 22:18 ` [PATCH 5/5] kernel.bbclass: remove unshipped files in do_install Dmitry Eremin-Solenikov
2011-09-27 13:41   ` Bruce Ashfield
2011-09-28 14:50   ` Richard Purdie
2011-09-17 22:23 ` [PATCH 1/5] kernel.bbclass: blacklist 'perf-dbg' as well for the modules metapackage Otavio Salvador
2011-09-22 12:25   ` Dmitry Eremin-Solenikov
2011-09-22 12:35     ` Koen Kooi
2011-09-22 13:00       ` Dmitry Eremin-Solenikov
2011-09-22 13:17         ` Koen Kooi
2011-09-22 13:28           ` Bruce Ashfield
2011-09-22 13:56             ` Koen Kooi
2011-09-22 14:04               ` Bruce Ashfield
2011-09-28  8:47 ` Dmitry Eremin-Solenikov
2011-09-28 14:52   ` Richard Purdie
2011-09-28 14:50 ` Richard Purdie

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=3968D33D-7086-4E22-9CA1-9B44BE0DBEBF@dominion.thruhere.net \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    /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.