From: Robert Yang <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/6] bitbake: Improve error/exception handling
Date: Wed, 14 Nov 2018 17:46:35 +0800 [thread overview]
Message-ID: <cover.1542188647.git.liezhi.yang@windriver.com> (raw)
The following changes since commit eddff2b361928e88e3628ebc22a1a0ebb119e01b:
curl: actually apply latest CVE patches (2018-11-09 17:46:18 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib rbt/bb_improve_error
http://git.pokylinux.org/cgit.cgi//log/?h=rbt/bb_improve_error
Robert Yang (6):
bitbake: utils: better_compile(): Fix line number when report errors
bitbake: parse/ast: fix line number for anonymous function
bitbake: data_smart: Add original traceback to ExpansionError
bitbake: data_smart: fix filename for compile()
bitbake: server/process: print a message when no logfile
bitbake: BBHandler: Fix __python_func_regexp__ for comment lines
bitbake/lib/bb/data_smart.py | 9 +++++++--
bitbake/lib/bb/parse/ast.py | 2 +-
bitbake/lib/bb/parse/parse_py/BBHandler.py | 2 +-
bitbake/lib/bb/server/process.py | 4 ++++
bitbake/lib/bb/utils.py | 7 +++++--
5 files changed, 18 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2018-11-14 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 9:46 Robert Yang [this message]
2018-11-14 9:46 ` [PATCH 1/6] bitbake: utils: better_compile(): Fix line number when report errors Robert Yang
2018-11-14 9:46 ` [PATCH 2/6] bitbake: parse/ast: fix line number for anonymous function Robert Yang
2018-11-14 9:46 ` [PATCH 3/6] bitbake: data_smart: Add original traceback to ExpansionError Robert Yang
2018-11-14 9:46 ` [PATCH 4/6] bitbake: data_smart: fix filename for compile() Robert Yang
2018-11-14 9:46 ` [PATCH 5/6] bitbake: server/process: print a message when no logfile Robert Yang
2018-11-14 9:46 ` [PATCH 6/6] bitbake: BBHandler: Fix __python_func_regexp__ for comment lines 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.1542188647.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox