From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Fix buildpaths QA check failure
Date: Thu, 24 Dec 2015 17:47:52 +0800 [thread overview]
Message-ID: <cover.1450950403.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The following changes since commit a6f8a3f12ef0a6f7fe4123b8854848a4c6cf94c7:
toaster.bbclass: fix TypeError when parsing build stats (2015-12-22 16:15:36 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/buildpaths
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/buildpaths
Kai Kang (2):
bash: fix buildpaths qa check error
gccmakedep: fix buildpaths qa check
meta/recipes-extended/bash/bash.inc | 6 ++++--
meta/recipes-graphics/xorg-util/gccmakedep_1.0.3.bb | 6 +++++-
2 files changed, 9 insertions(+), 3 deletions(-)
--
2.6.1
next reply other threads:[~2015-12-24 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 9:47 kai.kang [this message]
2015-12-24 9:47 ` [PATCH 1/2] bash: fix buildpaths qa check error kai.kang
2015-12-24 9:47 ` [PATCH 2/2] gccmakedep: fix buildpaths qa check kai.kang
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.1450950403.git.kai.kang@windriver.com \
--to=kai.kang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox