From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/7] rootfs generation improvements v3
Date: Wed, 25 Jul 2012 23:37:03 +0100 [thread overview]
Message-ID: <5819230.tev5bgC86G@helios> (raw)
In-Reply-To: <cover.1343241383.git.paul.eggleton@linux.intel.com>
On Wednesday 25 July 2012 19:42:50 Paul Eggleton wrote:
> * Fix errors with the ipk and deb backends if no complementary packages
> need to be installed
This change is totally broken as well. Shows what happens when you rush to get
something out before you leave for the evening. I might as well send out a v4
at this point.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-07-25 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 18:42 [PATCH 0/7] rootfs generation improvements v3 Paul Eggleton
2012-07-25 18:42 ` [PATCH 1/7] package.bbclass: Create symlinks for packages with different packaged name Paul Eggleton
2012-07-25 18:42 ` [PATCH 2/7] classes/rootfs_rpm: improve speed of RPM rootfs construction Paul Eggleton
2012-07-25 18:42 ` [PATCH 3/7] classes/package_deb: add PackageArch field Paul Eggleton
2012-07-25 18:42 ` [PATCH 4/7] Rework installation of dev, dbg, doc, and locale packages Paul Eggleton
2012-07-25 18:42 ` [PATCH 5/7] core-image-minimal: clear IMAGE_FEATURES Paul Eggleton
2012-07-25 18:42 ` [PATCH 6/7] classes/image: add staticdev-pkgs IMAGE_FEATURES feature Paul Eggleton
2012-07-25 18:42 ` [PATCH 7/7] buildhistory: improve performance of image info collection Paul Eggleton
2012-07-25 19:08 ` [PATCH 0/7] rootfs generation improvements v3 Koen Kooi
2012-07-25 20:28 ` Paul Eggleton
2012-07-25 22:37 ` Paul Eggleton [this message]
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=5819230.tev5bgC86G@helios \
--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