Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Patches and discussions about the oe-core layer"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] bitbake.conf: update OLDEST_KERNEL to 2.6.0
Date: Fri, 8 Jul 2011 11:03:37 +0100	[thread overview]
Message-ID: <201107081103.37637.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1310118829.18564.13.camel@lenovo.internal.reciva.com>

On Friday 08 July 2011 10:53:49 Phil Blundell wrote:
> They can always provide their own OLDEST_KERNEL setting, though.  To
> some extent I think it's a bit academic what the default in oe-core is.

Yes, but let's have a sensible default value, in particular that will allow 
the majority not to experience subtle problems that they will have to spend 
time tracking down. Many people coming to OE fresh will not know this setting 
even exists - I only discovered it the other day by accident.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-07-08 10:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 13:11 [PATCH 0/2] update OLDEST_KERNEL Paul Eggleton
2011-07-07 13:11 ` [PATCH 1/2] bitbake.conf: update OLDEST_KERNEL to 2.6.0 Paul Eggleton
2011-07-07 14:24   ` Koen Kooi
2011-07-07 14:34     ` Paul Eggleton
2011-07-07 23:15       ` Richard Purdie
2011-07-08  5:21       ` Khem Raj
2011-07-08  8:38         ` Paul Eggleton
2011-07-08  8:46           ` Chris Elston
2011-07-08  9:49             ` Paul Eggleton
2011-07-08  9:53           ` Phil Blundell
2011-07-08 10:03             ` Paul Eggleton [this message]
2011-07-08 10:12               ` Phil Blundell
2011-07-08 10:20                 ` Paul Eggleton
2011-07-08 14:17           ` Khem Raj
2011-07-08 16:28             ` Richard Purdie
2011-07-07 13:11 ` [PATCH 2/2] eglibc: bump PR for OLDEST_KERNEL change Paul Eggleton

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=201107081103.37637.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox