From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Fixes for groff and toolchain-scripts.bbclass
Date: Fri, 26 Oct 2018 17:45:35 +0800 [thread overview]
Message-ID: <cover.1540547104.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The following changes since commit 3be5331986289bf11040c241fd54239fb2011695:
testimage.bbclass: define ptest suite variable (2018-10-25 14:53:44 +0100)
are available in the Git repository at:
git://git.pokylinux.org/poky-contrib kangkai/misc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/misc
Kai Kang (2):
groff: not search fonts on build host
toolchain-scripts.bbclass: fix paths of siteconfig files
meta/classes/toolchain-scripts.bbclass | 9 +++++----
...groff-not-search-fonts-on-build-host.patch | 20 +++++++++++++++++++
meta/recipes-extended/groff/groff_1.22.3.bb | 1 +
3 files changed, 26 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-extended/groff/groff-1.22.3/groff-not-search-fonts-on-build-host.patch
--
2.18.0
next reply other threads:[~2018-10-26 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 9:45 kai.kang [this message]
2018-10-26 9:45 ` [PATCH 1/2] groff: not search fonts on build host kai.kang
2018-10-26 9:45 ` [PATCH 2/2] toolchain-scripts.bbclass: fix paths of siteconfig files 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.1540547104.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