From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Sane default for SPLASH
Date: Thu, 14 Jan 2010 15:12:24 +0100 [thread overview]
Message-ID: <hin8o7$2ml$2@ger.gmane.org> (raw)
In-Reply-To: <1263477134.22868.65.camel@andromeda>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14-01-10 14:52, Michael 'Mickey' Lauer wrote:
> Am Donnerstag, den 14.01.2010, 10:14 +0100 schrieb Koen Kooi:
>> NAK, the needless SPLASH -> BOOTSPLASH will create too much work for
>> people to catch up to, and it messes up the docs on the subject.
>
> Could you expand on that reason? I find the patch quite a useful
> refactoring. If we don't allow patches like this going in, we're
> doomed into living with misnomers forever -- and we all know that
> there are quite a few in OE metadata.
If you want to fix such misnomers it needs to be done with more thought
and publicity to allow external repos to catch up. No need to stab
people in the eye to make 2 people feel better.
And FWIW, psplash runs at shutdown as well, so it isn't really a
bootsplash ;)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLTyZIMkyGM64RGpERAqUXAKCsvCCu4AtWzl7ksBhuCzSKVhGaDgCfdKn6
GGBVwWvHLQGeyvYAe820rE0=
=K0dG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-01-14 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 23:31 RFC: Sane default for SPLASH Rolf Leggewie
2010-01-13 23:37 ` Richard Purdie
2010-01-13 23:47 ` Phil Blundell
2010-01-13 23:58 ` Richard Purdie
2010-01-14 0:38 ` Rolf Leggewie
2010-01-14 9:14 ` Koen Kooi
2010-01-14 13:48 ` Rolf Leggewie
2010-01-14 14:09 ` Koen Kooi
2010-01-14 15:18 ` Michael 'Mickey' Lauer
2010-01-14 13:52 ` Michael 'Mickey' Lauer
2010-01-14 14:12 ` Koen Kooi [this message]
2010-01-14 14:23 ` Philip Balister
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='hin8o7$2ml$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.