From: Martin Jansa <martin.jansa@gmail.com>
To: Max Eliaser <max.eliaser@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Upstream recipe for bootchart2 from WebOS (revised again)
Date: Thu, 7 Aug 2014 23:38:33 +0200 [thread overview]
Message-ID: <20140807213833.GY14848@jama> (raw)
In-Reply-To: <cover.1407445120.git.max.eliaser@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
On Thu, Aug 07, 2014 at 01:59:20PM -0700, Max Eliaser wrote:
> Hello list,
>
> This series adds a recipe for the bootchart2 daemon (a fork of the original
> bootchart.) It's based on a recipe from Meta-WebOS, but with extensive
> modifications.
>
> It is intended that bootchart2 will supersede the other bootchart daemons
> kicking around in oe-core/meta-oe. See bug 5893. [1]
>
> (Resubmitted this series yet again because I'd mistakenly included Yocto-
> specific changes in addition to oe-core ones.)
This one is missing pycairo change, is it intentional?
>
> Regards,
> -Max Eliaser
>
> [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=5893
> The following changes since commit 86afd7eb7c679eb065706137f28f44248f3fbc5a:
>
> ghostscript: Remove bogus gsfonts reference from DESCRIPTION (2014-08-06 11:14:40 +0100)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib meliaser/bootchart2-attempt3
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=meliaser/bootchart2-attempt3
>
> Max Eliaser (2):
> bootchart2: create recipe for bootchart2
> ubootchart: delete ubootchart recipe
>
> .../bootchart2/bootchart2/bootchartd_stop.sh | 18 +++
> meta/recipes-devtools/bootchart2/bootchart2_git.bb | 148 +++++++++++++++++++++
> .../ubootchart/files/sysvinit.patch | 14 --
> .../ubootchart/files/ubootchart-stop | 3 -
> .../ubootchart/files/ubootchart.desktop | 6 -
> meta/recipes-devtools/ubootchart/ubootchart_svn.bb | 39 ------
> 6 files changed, 166 insertions(+), 62 deletions(-)
> create mode 100644 meta/recipes-devtools/bootchart2/bootchart2/bootchartd_stop.sh
> create mode 100644 meta/recipes-devtools/bootchart2/bootchart2_git.bb
> delete mode 100644 meta/recipes-devtools/ubootchart/files/sysvinit.patch
> delete mode 100644 meta/recipes-devtools/ubootchart/files/ubootchart-stop
> delete mode 100644 meta/recipes-devtools/ubootchart/files/ubootchart.desktop
> delete mode 100644 meta/recipes-devtools/ubootchart/ubootchart_svn.bb
>
> --
> 1.8.3.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-08-07 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 20:59 [PATCH 0/2] Upstream recipe for bootchart2 from WebOS (revised again) Max Eliaser
2014-08-07 20:59 ` [PATCH 1/2] bootchart2: create recipe for bootchart2 Max Eliaser
2014-08-07 20:59 ` [PATCH 2/2] ubootchart: delete ubootchart recipe Max Eliaser
2014-08-07 21:38 ` Martin Jansa [this message]
2014-08-07 22:33 ` [PATCH 0/2] Upstream recipe for bootchart2 from WebOS (revised again) Eliaser, MaX
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=20140807213833.GY14848@jama \
--to=martin.jansa@gmail.com \
--cc=max.eliaser@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