From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC} glib-2.0 cleanup
Date: Mon, 01 Mar 2010 15:35:44 +0100 [thread overview]
Message-ID: <hmgjc2$sgd$1@dough.gmane.org> (raw)
In-Reply-To: <1267392928.13054.1.camel@andromeda>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 28-02-10 22:35, Michael 'Mickey' Lauer wrote:
> please both the lets-keep-everything-no-matter-how-rotten and also the
> lets-strive-for-few-high-quality recipes.
Note that plainly deleting them as proposed does neither, it doesn't
make the remaining recipes "high quality", it just reduces the amount of
recipes.
And I want to reiterate the importance of new-style staging and
leveraging that for BBCLASSEXTEND.
The majority of the TSC has already warmly recommended it.....
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLi9DAMkyGM64RGpERAmn/AKC85ZIwHVzCV4ufjbKg1+Lt/7whIwCfQ3Hd
k5F2xyrlq8adN5ZZS3YJ7EM=
=ZYzq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-01 14:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 19:39 [RFC} glib-2.0 cleanup Frans Meulenbroeks
2010-02-28 20:05 ` Koen Kooi
2010-02-28 20:26 ` Frans Meulenbroeks
2010-02-28 21:40 ` Graham Gower
2010-03-01 15:15 ` Denys Dmytriyenko
2010-03-01 15:20 ` Frans Meulenbroeks
2010-03-01 15:25 ` Marcin Juszkiewicz
2010-03-06 19:36 ` Frans Meulenbroeks
2010-02-28 21:35 ` Michael 'Mickey' Lauer
2010-03-01 7:30 ` Frans Meulenbroeks
2010-03-01 14:35 ` Koen Kooi [this message]
2010-03-01 14:43 ` Dr. Michael Lauer
2010-03-01 15:02 ` bitbake -b with BBCLASSEXTENDed recipes Was: " Martin Jansa
2010-03-15 16:48 ` bitbake -b with BBCLASSEXTENDed recipes Enrico Scholz
2010-03-16 3:23 ` Denys Dmytriyenko
2010-03-17 8:48 ` Martin Jansa
2010-03-17 10:03 ` Enrico Scholz
2010-03-01 22:11 ` [RFC} glib-2.0 cleanup Khem Raj
2010-03-01 22:30 ` Denys Dmytriyenko
2010-03-01 22:34 ` Chris Larson
2010-03-01 22:49 ` Khem Raj
2010-03-01 22:51 ` Chris Larson
2010-03-01 23:04 ` Khem Raj
2010-03-01 23:26 ` Chris Larson
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='hmgjc2$sgd$1@dough.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.