From: Max Eliaser <max.eliaser@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Upstream recipe for bootchart2 from WebOS
Date: Tue, 29 Jul 2014 11:07:05 -0700 [thread overview]
Message-ID: <cover.1406657048.git.max.eliaser@intel.com> (raw)
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]
Regards,
-Max Eliaser
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=5893
The following changes since commit 5452824960e8e77005a25ac11fd069d927523d3e:
default-distrovars.inc: Remove unused variable 'LIMIT_BUILT_LOCALES' (2014-06-13 13:08:44 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib meliaser/bootchart2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=meliaser/bootchart2
Max Eliaser (2):
python: python-pycairo: add python-pycairo-native
bootchart2: create recipe for bootchart2
.../bootchart2/bootchart2/bootchartd_stop.sh | 18 +++
meta/recipes-devtools/bootchart2/bootchart2_git.bb | 135 +++++++++++++++++++++
.../python/python-pycairo_1.10.0.bb | 2 +
3 files changed, 155 insertions(+)
create mode 100644 meta/recipes-devtools/bootchart2/bootchart2/bootchartd_stop.sh
create mode 100644 meta/recipes-devtools/bootchart2/bootchart2_git.bb
--
1.8.3.2
next reply other threads:[~2014-07-29 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 18:07 Max Eliaser [this message]
2014-07-29 18:07 ` [PATCH 1/2] python: python-pycairo: add python-pycairo-native Max Eliaser
2014-07-29 18:07 ` [PATCH 2/2] bootchart2: create recipe for bootchart2 Max Eliaser
2014-07-29 19:34 ` [PATCH 0/2] Upstream recipe for bootchart2 from WebOS Saul Wold
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=cover.1406657048.git.max.eliaser@intel.com \
--to=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 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.