From: Michael Wood <michael.g.wood@intel.com>
To: Randy Witt <randy.e.witt@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] toaster: add DL_DIR and SSTATE_DIR to oe toasterconf
Date: Thu, 7 Apr 2016 11:05:20 +0100 [thread overview]
Message-ID: <570630E0.7080007@intel.com> (raw)
In-Reply-To: <570572EC.2000008@linux.intel.com>
On 06/04/16 21:34, Randy Witt wrote:
> On 04/06/2016 10:00 AM, Michael Wood wrote:
>> From: Ed Bartosh <ed.bartosh@linux.intel.com>
>
> Shouldn't the message from the cover letter actually be the commit
> message here, rather than an empty message?
Sure, I can easily amend Ed's commit message to include this if you'd
like, the reason I sent a cover letter was just to let people know who
aren't following the development of Toaster what this was about.
>
>>
>> Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
>> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
>> ---
>> meta/conf/toasterconf.json | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/conf/toasterconf.json b/meta/conf/toasterconf.json
>> index 1987793..bbd40e9 100644
>> --- a/meta/conf/toasterconf.json
>> +++ b/meta/conf/toasterconf.json
>> @@ -2,9 +2,11 @@
>> "config": {
>> "MACHINE" : "qemux86",
>> "DISTRO" : "poky",
>> + "DL_DIR" : "${TOPDIR}/../downloads",
>> "IMAGE_FSTYPES": "ext3 jffs2 tar.bz2",
>> "IMAGE_INSTALL_append": "",
>> - "PACKAGE_CLASSES": "package_rpm"
>> + "PACKAGE_CLASSES": "package_rpm",
>> + "SSTATE_DIR" : "${TOPDIR}/../sstate-cache"
>> },
>> "layersources": [
>> {
>>
>
prev parent reply other threads:[~2016-04-07 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 17:00 [PATCH] Add DL_DIR and SSTATE_DIR to toasterconf Michael Wood
2016-04-06 17:00 ` [PATCH] toaster: add DL_DIR and SSTATE_DIR to oe toasterconf Michael Wood
2016-04-06 20:34 ` Randy Witt
2016-04-07 10:05 ` Michael Wood [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=570630E0.7080007@intel.com \
--to=michael.g.wood@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.e.witt@linux.intel.com \
/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