From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 0/1] archiver.bbclass: Add two default set for avoiding error when missing assignment
Date: Fri, 18 May 2012 08:41:41 +0300 [thread overview]
Message-ID: <4FB5E115.6030800@linux.intel.com> (raw)
In-Reply-To: <cover.1337157396.git.xiaofeng.yan@windriver.com>
On 05/16/2012 11:59 AM, xiaofeng.yan@windriver.com wrote:
> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>
> This is V2.
>
> Add two default set(SOURCE_ARCHIVE_LOG_WITH_SCRIPTS, SOURCE_ARCHIVE_PACKAGE_TYPE) to archiver.bbclass for avoiding building error when forgetting to assign to them.
> Make some modification according to clarson's suggestion. Thank him correct my fault.
>
> The following changes since commit d4e265661517f8dd4e1648fdc56bac5973f986f6:
> Saul Wold (1):
> poky.conf: Change WARNS -> ERRORS
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib xiaofeng/archiver
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/archiver
>
> Xiaofeng Yan (1):
> archiver.bbclass: Add two default set for avoiding error when missing
> assignment
>
> meta/classes/archiver.bbclass | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Merged into OE-Core
Thanks
Sau!
next prev parent reply other threads:[~2012-05-18 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:59 [PATCH 0/1] archiver.bbclass: Add two default set for avoiding error when missing assignment xiaofeng.yan
2012-05-16 8:59 ` [PATCH 1/1] " xiaofeng.yan
2012-05-18 5:41 ` Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-11 10:13 [PATCH 0/1] " xiaofeng.yan
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=4FB5E115.6030800@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Zhenfeng.Zhao@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.