From: Robert Yang <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/1] cooker: simplify BB_DANGLINGAPPENDS_WARNONLY
Date: Fri, 30 Nov 2018 11:39:17 +0800 [thread overview]
Message-ID: <cover.1543548740.git.liezhi.yang@windriver.com> (raw)
Hi RP,
I'd like to change the fatal message to be an event, the benefits are:
- Things like report-error.bbclass can catch the error
- It's easier to get bbappends list from an event message than from console log.
What's your opinion, please ?
// Robert
The following changes since commit 41d89552620bfbc94031d314e6b3d0324f7a330e:
bitbake: fetch2: Avoid warning about incorrect character escaping in regex (2018-11-27 22:15:34 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib rbt/append
http://git.pokylinux.org/cgit.cgi//log/?h=rbt/append
Robert Yang (1):
cooker: simplify BB_DANGLINGAPPENDS_WARNONLY
bitbake/lib/bb/cooker.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] cooker: simplify BB_DANGLINGAPPENDS_WARNONLY
Date: Fri, 30 Nov 2018 11:39:07 +0800 [thread overview]
Message-ID: <cover.1543548740.git.liezhi.yang@windriver.com> (raw)
Hi RP,
I'd like to change the fatal message to be an event, the benefits are:
- Things like report-error.bbclass can catch the error
- It's easier to get bbappends list from an event message than from console log.
What's your opinion, please ?
// Robert
The following changes since commit 41d89552620bfbc94031d314e6b3d0324f7a330e:
bitbake: fetch2: Avoid warning about incorrect character escaping in regex (2018-11-27 22:15:34 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib rbt/append
http://git.pokylinux.org/cgit.cgi//log/?h=rbt/append
Robert Yang (1):
cooker: simplify BB_DANGLINGAPPENDS_WARNONLY
bitbake/lib/bb/cooker.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2018-11-30 3:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 3:39 Robert Yang [this message]
2018-11-30 3:39 ` [PATCH 0/1] cooker: simplify BB_DANGLINGAPPENDS_WARNONLY Robert Yang
2018-11-30 3:31 ` Robert Yang
2018-11-30 3:33 ` ✗ patchtest: failure for " Patchwork
2018-11-30 3:39 ` [PATCH 1/1] " Robert Yang
2018-11-30 3:39 ` Robert Yang
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=cover.1543548740.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@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.