From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Split IMAGE* variables into a separate class
Date: Thu, 24 Mar 2011 15:00:27 -0700 [thread overview]
Message-ID: <4D8BBEFB.4040107@mentor.com> (raw)
In-Reply-To: <43A4384F-8595-4A7A-8EC5-93DF7DCFEE39@dominion.thruhere.net>
On 03/24/2011 08:39 AM, Koen Kooi wrote:
>
> Op 24 mrt 2011, om 15:49 heeft Richard Purdie het volgende geschreven:
>
>> From: Richard Purdie<richard.purdie@linuxfoundation.org>
>>
>> These patches split the IMAGE* variables out into a separate class
>> to improve readabilty.
>
> I like it!
Agreed. This will help us clean up the N instances of make an ext2
image, modify.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-24 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 14:49 [PATCH 0/2] Split IMAGE* variables into a separate class Richard Purdie
2011-03-24 14:49 ` [PATCH 2/2] image_types.bbclass: Drop IMAGE_EXTRA_OPTION in favour of the more standard EXTRA_IMAGECMD Richard Purdie
2011-03-24 14:49 ` [PATCH 1/2] bitbake.conf/image.bbclass: Move image type information into image_types.bbclass Richard Purdie
2011-03-31 4:36 ` [PATCH 0/3] port oe-dev ,ubifs.img link support Ben Gardiner
2011-03-31 4:36 ` [PATCH 1/3] image_types.bbclass: rm symlink destination via ln Ben Gardiner
2011-03-31 4:36 ` [PATCH 2/3] image_types.bbclass: add link to .rootfs.<type> or .<type>.img Ben Gardiner
2011-03-31 4:36 ` [PATCH 3/3] image_types.bbclass: use .ubifs.img extension in IMAGE_CMD_ubi Ben Gardiner
2011-03-31 15:47 ` [PATCH 0/3] port oe-dev ,ubifs.img link support Tom Rini
2011-03-31 19:14 ` Denys Dmytriyenko
2011-03-24 15:39 ` [PATCH 0/2] Split IMAGE* variables into a separate class Koen Kooi
2011-03-24 22:00 ` Tom Rini [this message]
2011-03-25 13:26 ` 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=4D8BBEFB.4040107@mentor.com \
--to=tom_rini@mentor.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 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.