From: Ladislav Michl <ladis@linux-mips.org>
To: Roland Hieber <r.hieber@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] htop: version bump 2.1.0 -> 2.2.0
Date: Tue, 17 Apr 2018 10:10:25 +0200 [thread overview]
Message-ID: <20180417081025.GA16207@lenoch> (raw)
In-Reply-To: <20180415191755.24390-1-r.hieber@pengutronix.de>
On Sun, Apr 15, 2018 at 09:17:55PM +0200, Roland Hieber wrote:
> Removed all patches:
> - 0001-linux-LinuxProcessList-fix-reading-of-number-of-read.patch:
> applied upstream in https://github.com/hishamhm/htop/commit/70ed51a303
> - 0002-configure-check-for-ncurses-with-ncurses6-config.patch:
> replaced by setting HTOP_NCURSES_CONFIG_SCRIPT=ncurses6-config in
> HTOP_CONF_ENV
>
> Fixes: 74ffd1f57d0d68a8918 ("htop: fix configure to discover ncurses6")
> Cc: Ladislav Michl <ladis@linux-mips.org>
> Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
>
> ---
> v2:
> - take care of the patches
> - set HTOP_NCURSES_CONFIG_SCRIPT. This is functionally equivalent to
> Ladislav's 0002.patch, but I prefer setting a small variable in
> htop.make to a configure.ac patch.
Yes, I consider it a better solution as well. Go for it :)
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-04-17 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 15:14 [ptxdist] [PATCH] " Roland Hieber
2018-04-10 15:34 ` Bastian Stender
2018-04-11 6:56 ` Alexander Dahl
2018-04-11 7:36 ` Michael Olbrich
2018-04-11 8:49 ` Roland Hieber
2018-04-15 19:17 ` [ptxdist] [PATCH v2] " Roland Hieber
2018-04-16 15:39 ` Michael Olbrich
2018-04-17 8:10 ` Ladislav Michl [this message]
2018-04-18 8:28 ` [ptxdist] [PATCH v3] " Roland Hieber
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=20180417081025.GA16207@lenoch \
--to=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.de \
--cc=r.hieber@pengutronix.de \
/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