From: <liezhi.yang@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH v2 0/1] bitbake: event: Improve error message for eventhandler
Date: Tue, 26 Dec 2023 07:11:22 -0800 [thread overview]
Message-ID: <cover.1703602054.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
The following changes since commit 2d8e0802313ddfc904344b3cff3e0396e0d17fe8:
oeqa/selftest/prservice: Improve test robustness (2023-12-24 10:39:07 +0000)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/event
https://github.com/robertlinux/yocto/tree/rbt/event
Robert Yang (1):
bitbake: event: Improve error message for eventhandler
bitbake/lib/bb/event.py | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
--
2.42.0
next reply other threads:[~2023-12-26 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 15:11 liezhi.yang [this message]
2023-12-26 15:11 ` [PATCH v2 1/1] bitbake: event: Improve error message for eventhandler liezhi.yang
2023-12-27 23:42 ` [bitbake-devel] " Richard Purdie
2023-12-28 7:15 ` Robert Yang
2023-12-28 10:44 ` Richard Purdie
2023-12-29 4:24 ` 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.1703602054.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).