From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] Whitelist parallel build variables
Date: Mon, 27 Aug 2012 08:33:55 -0700 [thread overview]
Message-ID: <503B9363.90901@linux.intel.com> (raw)
In-Reply-To: <cover.1345836240.git.mark.hatle@windriver.com>
On 08/24/2012 12:24 PM, Mark Hatle wrote:
> The following changes since commit 968cfc0b630fb409430a46b1512d6bf0de225ad1:
>
> build-appliance-image: Add vmx* files and build zip file (2012-08-24 17:32:34 +0100)
>
> are available in the git repository at:
> git://git.yoctoproject.org/poky-contrib mhatle/whitelist
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mhatle/whitelist
>
> Mark Hatle (1):
> bitbake.conf: add variables to exclude from hash.
>
> meta/conf/bitbake.conf | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-08-27 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 19:24 [PATCH 0/1] Whitelist parallel build variables Mark Hatle
2012-08-24 19:24 ` [PATCH 1/1] bitbake.conf: add variables to exclude from hash Mark Hatle
2012-08-27 15:33 ` Saul Wold [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=503B9363.90901@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=mark.hatle@windriver.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.