From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] RFC: Split do_rootfs into image specific tasks?
Date: Mon, 28 Dec 2015 13:18:51 +0000 [thread overview]
Message-ID: <1451308731.4129.23.camel@linuxfoundation.org> (raw)
In-Reply-To: <1451307640.4129.16.camel@linuxfoundation.org>
To put this in a different why which people might be able to relate to,
this changes:
do_rootfs
into:
do_rootfs
do_image
do_image_ext4
do_image_tar
do_image_complete
(for IMAGE_FSTYPES = "tar.bz2 ext4")
Cheers,
Richard
next prev parent reply other threads:[~2015-12-28 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 13:00 RFC: Split do_rootfs into image specific tasks? Richard Purdie
2015-12-28 13:18 ` Richard Purdie [this message]
2016-01-04 10:55 ` Patrick Ohly
2016-01-06 23:11 ` Richard Purdie
2016-01-05 21:30 ` Paul Eggleton
2016-01-06 23:04 ` Richard Purdie
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=1451308731.4129.23.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-architecture@lists.openembedded.org \
--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