Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Fix screen build failure
Date: Tue, 8 Sep 2015 16:15:11 +0800	[thread overview]
Message-ID: <cover.1441700018.git.kai.kang@windriver.com> (raw)

From: Kai Kang <kai.kang@windriver.com>

The following changes since commit c1df471feacaf2590216aa476ce242908dac38cf:

  pseudo_1.7.3.bb: New version of pseudo (2015-09-06 15:26:27 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib kangkai/screen
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/screen

Kai Kang (1):
  screen: backport to fix build error

 .../screen/0002-comm.h-now-depends-on-term.h.patch | 33 ++++++++++++++++++++++
 meta/recipes-extended/screen/screen_4.3.1.bb       |  1 +
 2 files changed, 34 insertions(+)
 create mode 100644 meta/recipes-extended/screen/screen/0002-comm.h-now-depends-on-term.h.patch

-- 
1.9.1



             reply	other threads:[~2015-09-08  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  8:15 kai.kang [this message]
2015-09-08  8:15 ` [PATCH 1/1] screen: backport to fix build error 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.1441700018.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