Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] screen update, take two
Date: Thu, 13 Aug 2015 16:26:31 +0300	[thread overview]
Message-ID: <cover.1439471616.git.jussi.kukkonen@intel.com> (raw)

I'm resending only the screen patch as the others are in already.

Changes since v1:
* remove the old GPLv2 version

I'm not taking any stance on tmux vs screen debate: we can still
change to tmux. Just wanted to get rid of some very old and
potentially bit rotted code.

Jussi

The following changes since commit a533776d6ff83b6e3e830137455b8382d002768b:

  perf: fix build breakage on kernels after 4.1 (2015-08-12 11:31:49 -0700)

are available in the git repository at:

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

Jussi Kukkonen (1):
  screen: Upgrade 4.0.3 -> 4.3.1

 .../screen/screen-4.0.3/configure.patch            | 979 ---------------------
 .../screen-4.0.3/screen-4.0.2-CVE-2009-1215.patch  |  27 -
 .../screen-4.0.3/screen-4.0.3-CVE-2009-1214.patch  |  86 --
 .../Avoid-mis-identifying-systems-as-SVR4.patch    |  57 ++
 ...cross-compile-alternatives-for-AC_TRY_RUN.patch | 137 +++
 .../Remove-redundant-compiler-sanity-checks.patch  |  65 ++
 ...t-file-system-checks-when-cross-compiling.patch | 135 +++
 .../fix-parallel-make.patch                        |   0
 .../screen/{screen-4.0.3 => screen}/screen.pam     |   0
 .../screen/{screen_4.0.3.bb => screen_4.3.1.bb}    |  34 +-
 10 files changed, 408 insertions(+), 1112 deletions(-)
 delete mode 100644 meta/recipes-extended/screen/screen-4.0.3/configure.patch
 delete mode 100644 meta/recipes-extended/screen/screen-4.0.3/screen-4.0.2-CVE-2009-1215.patch
 delete mode 100644 meta/recipes-extended/screen/screen-4.0.3/screen-4.0.3-CVE-2009-1214.patch
 create mode 100644 meta/recipes-extended/screen/screen/Avoid-mis-identifying-systems-as-SVR4.patch
 create mode 100644 meta/recipes-extended/screen/screen/Provide-cross-compile-alternatives-for-AC_TRY_RUN.patch
 create mode 100644 meta/recipes-extended/screen/screen/Remove-redundant-compiler-sanity-checks.patch
 create mode 100644 meta/recipes-extended/screen/screen/Skip-host-file-system-checks-when-cross-compiling.patch
 rename meta/recipes-extended/screen/{screen-4.0.3 => screen}/fix-parallel-make.patch (100%)
 rename meta/recipes-extended/screen/{screen-4.0.3 => screen}/screen.pam (100%)
 rename meta/recipes-extended/screen/{screen_4.0.3.bb => screen_4.3.1.bb} (58%)

-- 
2.1.4



             reply	other threads:[~2015-08-13 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 13:26 Jussi Kukkonen [this message]
2015-08-13 13:26 ` [PATCHv2 1/1] screen: Upgrade 4.0.3 -> 4.3.1 Jussi Kukkonen
2015-08-18  8:36   ` Martin Jansa
2015-08-19  8:17     ` Jussi Kukkonen
2015-08-19 10:49       ` Burton, Ross
     [not found]       ` <tor.121455D5F425.1070308@windriver.com>
2015-08-20 20:15         ` Radzykewycz, T (Radzy)
2015-08-20 21:34           ` Burton, Ross
2015-08-20 21:41             ` Khem Raj
2015-08-21 15:18               ` Radzykewycz, T (Radzy)
2015-08-20 23:56         ` Radzykewycz, T (Radzy)

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.1439471616.git.jussi.kukkonen@intel.com \
    --to=jussi.kukkonen@intel.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