From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: ipkg/opkg offical response
Date: Thu, 27 Mar 2008 20:25:13 +0100 [thread overview]
Message-ID: <fsgsaq$nqf$1@ger.gmane.org> (raw)
In-Reply-To: <1206638249.4514.57.camel@dax.rpnet.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
| * Adding do_deploy to packaged-staging's knowledge. This is best done
| with the patch for kernel.bbclass that thesing was been working on. I've
| made some suggestions for tweaks (looking at the version already in
| poky) and suggested he commits it after that.
That patch broke uImage kernels *real bad*, I just pushed a fix for it.
Proper review on mailinglist first next time?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFH6/SZMkyGM64RGpERAlQqAJ9TQZ14UlkUvuJGALQaw6cshS01gACgkWkd
HtY0P54Pk5HXV+qPkEGmxtw=
=4YKa
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-27 19:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 17:17 ipkg/opkg offical response Richard Purdie
2008-03-27 19:25 ` Koen Kooi [this message]
2008-03-27 22:57 ` Jeremy Lainé
2008-03-27 23:09 ` Tom Rini
2008-03-28 0:30 ` Leon Woestenberg
2008-03-28 9:20 ` Richard Purdie
2008-03-28 9:43 ` Koen Kooi
2008-03-28 4:23 ` Marcin Juszkiewicz
2008-03-27 23:07 ` Richard Purdie
2008-03-28 7:03 ` kernel breackage, was " Koen Kooi
2008-03-28 9:17 ` Richard Purdie
2008-03-28 9:35 ` Koen Kooi
2008-03-27 20:04 ` Marcin Juszkiewicz
2008-03-28 0:15 ` Rod Whitby
2008-03-28 6:56 ` Koen Kooi
2008-03-28 9:27 ` Richard Purdie
2008-08-21 6:48 ` Mike (mwester)
2008-03-28 16:17 ` Jeremy Lainé
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='fsgsaq$nqf$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.