From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>,
Mihai Prica <mihai.prica@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] Add midori and dependencies
Date: Wed, 28 Aug 2013 09:48:34 +0100 [thread overview]
Message-ID: <11388358.dTZLhufORm@helios> (raw)
In-Reply-To: <20130828081814.GE3544@jama>
On Wednesday 28 August 2013 10:18:15 Martin Jansa wrote:
> On Tue, Aug 27, 2013 at 05:59:34PM +0300, Mihai Prica wrote:
> > The Midori web-browser can be used to more easily test the functionality
> > of webkit-gtk.
> >
> > * The midori and libnotify recipes are from meta-gnome.
> > * The python-docutils and vala recipes are from meta-oe.
> > * The midori and python-docutils packages have been updated to the latest
> > upstream version.
> >
> > Midori also depends on ca-certificates. A patch set was sent by
> > Christopher
> > Larson that adds the recipe in oe-core. This series depends on his
> > addition.
>
> Are you going to send patches to oe-devel to remove moved
> recipes/bbclasses ?
I'll take care of this along with ca-certificates.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-08-28 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 14:59 [PATCH 0/5] Add midori and dependencies Mihai Prica
2013-08-27 14:59 ` [PATCH 1/5] python-docutils: add version 0.11 from meta-oe Mihai Prica
2013-08-27 14:59 ` [PATCH 2/5] libnotify: add version 0.6.0 " Mihai Prica
2013-08-27 14:59 ` [PATCH 3/5] vala: add version 0.16 " Mihai Prica
2013-08-27 14:59 ` [PATCH 4/5] vala.bbclass: add class " Mihai Prica
2013-08-27 14:59 ` [PATCH 5/5] midori: add version 0.5.5 " Mihai Prica
2013-08-27 15:15 ` [PATCH 0/5] Add midori and dependencies Paul Eggleton
2013-08-28 8:18 ` Martin Jansa
2013-08-28 8:48 ` Paul Eggleton [this message]
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=11388358.dTZLhufORm@helios \
--to=paul.eggleton@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=mihai.prica@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