From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/2] psplash improvements v2
Date: Tue, 21 Feb 2012 15:52:13 +0000 [thread overview]
Message-ID: <cover.1329837658.git.paul.eggleton@linux.intel.com> (raw)
Implements the psplash changes as discussed on the mailing list [1] and
by the TSC [2].
[1] http://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg13800.html
[2] http://lists.linuxtogo.org/pipermail/tsc/2012-January/000330.html
Since v1 I've done away with the additional script and integrated .png
conversion into the recipe (optional) as well as used alternatives to
allow selecting the psplash at runtime. I also decided against renaming
the default header file as it would break existing bbappends.
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.
The following changes since commit 1da6a2dbd5e7aeea6cd45ca05590bdd50b67bf89:
recipes: bump PR to rebuild .la files without libz.la (2012-02-21 15:00:24 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/oe-psplash
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/oe-psplash
Paul Eggleton (2):
psplash: use OpenEmbedded logo
psplash: allow building multiple splash executables
meta/recipes-core/psplash/files/psplash-poky-img.h | 1959 +++++++++++---------
meta/recipes-core/psplash/psplash_git.bb | 93 +-
2 files changed, 1143 insertions(+), 909 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-02-21 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 15:52 Paul Eggleton [this message]
2012-02-21 15:52 ` [RFC PATCH 1/2] psplash: use OpenEmbedded logo Paul Eggleton
2012-02-21 15:52 ` [RFC PATCH 2/2] psplash: allow building multiple splash executables 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=cover.1329837658.git.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