From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] util-linux: use a patch from upstream to fix ncursesw support
Date: Thu, 24 Aug 2017 23:21:13 +0200 [thread overview]
Message-ID: <20170824232113.474c52b3@windsurf> (raw)
In-Reply-To: <20170824035838.14466-2-casantos@datacom.ind.br>
Hello,
On Thu, 24 Aug 2017 00:58:38 -0300, Carlos Santos wrote:
> This patch is much smaller the the previous one and will unlikely cause
> a conflict with some forthcoming 2.30.x release.
>
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
> ...-Revert-build-sys-ncurses-headers-cleanup.patch | 191 ---------------------
> ...upport-ncursesw-without-headers-in-ncurse.patch | 58 +++++++
> 2 files changed, 58 insertions(+), 191 deletions(-)
> delete mode 100644 package/util-linux/0001-Revert-build-sys-ncurses-headers-cleanup.patch
> create mode 100644 package/util-linux/0001-build-sys-support-ncursesw-without-headers-in-ncurse.patch
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-24 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 23:55 [Buildroot] [PATCH] util-linux: add menu items for login utilities Carlos Santos
2017-08-23 13:42 ` Thomas Petazzoni
2017-08-23 16:51 ` Carlos Santos
2017-08-24 3:58 ` [Buildroot] [PATCH 1/2] " Carlos Santos
2017-08-24 3:58 ` [Buildroot] [PATCH 2/2] util-linux: use a patch from upstream to fix ncursesw support Carlos Santos
2017-08-24 21:21 ` Thomas Petazzoni [this message]
2017-08-24 21:24 ` [Buildroot] [PATCH 1/2] util-linux: add menu items for login utilities Thomas Petazzoni
2017-08-25 3:19 ` [Buildroot] [PATCH v3] " Carlos Santos
2017-08-25 20:51 ` Arnout Vandecappelle
2017-08-25 21:26 ` [Buildroot] [PATCH v4] " Carlos Santos
2017-09-02 0:41 ` [Buildroot] [PATCH v5] " Carlos Santos
2017-09-02 20:49 ` Thomas Petazzoni
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=20170824232113.474c52b3@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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