All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Kernel recipes with broken PRs now
Date: Sun, 31 May 2009 09:36:30 +0200	[thread overview]
Message-ID: <gvtc1u$5r8$1@ger.gmane.org> (raw)
In-Reply-To: <20090530222745.GU23842@smtp.west.cox.net>

On 31-05-09 00:27, Tom Rini wrote:
> On Sat, May 30, 2009 at 11:13:34PM +0200, Koen Kooi wrote:
>> On 30-05-09 21:13, Tom Rini wrote:
>>> On Fri, May 22, 2009 at 10:31:43PM -0700, Tom Rini wrote:
>>>> On Sat, May 23, 2009 at 07:22:56AM +0200, Koen Kooi wrote:
>>>>> On 23-05-09 00:27, Andrea Adami wrote:
>>>>>> I think the side-effects of the patch are blessing too much...
>>>>>
>>>>> That's called 'incentive' :) You are always complaining about
>>>>> unmaintained kernel recipes, now you have a way to identify them :)
>>>>>
>>>>>> I'd propose a rethink of the patch as opt-in.
>>>>>
>>>>> Due to the way OE is structured, that's sadly impossible.
>>>>
>>>> Can we please get a little write-up on the new variable on the wiki, to
>>>> point people at when they hit a broken recipe.
>>>
>>> Ping.
>>
>> You lack write permissions in the wiki? Or do you lack write permissions
>> to the usermanual?
>
> I lack complete understanding of the When To

Always

> and a short summary of What This Does.

This makes external modules and kernel dependant userspace actually work 
if you use a package manager and/or incremental OE builds. Without it 
you rely on sheer luck to keep those working.

regards,

Koen




  reply	other threads:[~2009-05-31  7:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 21:31 Kernel recipes with broken PRs now Tom Rini
2009-05-22 22:27 ` Andrea Adami
2009-05-23  5:22   ` Koen Kooi
2009-05-23  5:31     ` Tom Rini
2009-05-30 19:13       ` Tom Rini
2009-05-30 21:13         ` Koen Kooi
2009-05-30 22:27           ` Tom Rini
2009-05-31  7:36             ` Koen Kooi [this message]
2009-05-23 13:06 ` Leon Woestenberg
2009-05-23 16:23   ` Phil Blundell
2009-05-23 22:25     ` Leon Woestenberg
2009-05-24  8:23       ` Koen Kooi
2009-05-24  9:23         ` Phil Blundell
2009-05-24 11:37           ` Koen Kooi
2009-05-24 12:27             ` Phil Blundell
2009-05-24 13:04               ` Koen Kooi
2009-05-24 16:51                 ` Phil Blundell
2009-05-24 21:45           ` Leon Woestenberg
2009-05-24 18:49 ` Marcin Juszkiewicz
2009-05-30 19:16   ` Tom Rini
2009-05-30 21:13     ` Koen Kooi
2009-05-30 21:33       ` Tom Rini
2009-05-30 22:16         ` Otavio Salvador
2009-05-30 22:28           ` Tom Rini
2009-05-30 23:04     ` Phil Blundell
2009-05-31  0:49       ` Otavio Salvador
2009-05-31 10:00         ` Phil Blundell

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='gvtc1u$5r8$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.