All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver] patches on patchwork
Date: Sun, 23 Dec 2012 19:57:06 +0000	[thread overview]
Message-ID: <3012778.0fGtJNS4Ad@helios> (raw)
In-Reply-To: <20121220140211.GO14543@jama.palm1.palmone.com>

On Thursday 20 December 2012 15:02:11 Martin Jansa wrote:
> On Thu, Dec 20, 2012 at 02:33:07PM +0100, Martin Jansa wrote:
> > Hi, can you check and update patche in meta-webserver bundle?
> > http://patches.openembedded.org/bundle/jama/meta-webserver/?archive=both

I didn't comment at the time but I don't particularly like this patch - I 
didn't see this error and if it is present, I don't think this is the right 
way to fix it - it should be fixed in the makefile surely...

> I've forgot to mention there is also one in meta-opie and one in
> meta-handheld
>
> http://patches.openembedded.org/bundle/jama/meta-handheld/?archive=both

This has already been applied, I have marked it as such.

> http://patches.openembedded.org/bundle/jama/meta-opie/?archive=both

Half of this has been superseded (the addition of MACHINE_EXTRA_RRECOMMENDS - 
now we just add packagegroup-base) and for ensuring that the kernel image is 
within the rootfs, the machine config should be adding kernel-image to 
MACHINE_ESSENTIAL_EXTRA_RDEPENDS. I discussed this with Denis at the time, so 
I've marked it as rejected.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-12-23 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 13:30 [meta-networking] patches on patchwork Martin Jansa
2012-12-20 13:33 ` Martin Jansa
2012-12-20 14:02   ` [meta-webserver] " Martin Jansa
2012-12-23 19:57     ` Paul Eggleton [this message]
2012-12-24 13:46 ` [meta-networking] " Joe MacDonald
2012-12-24 15:04   ` Martin Jansa

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=3012778.0fGtJNS4Ad@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@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.