From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de, Roland Hieber <r.hieber@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] htop: version bump 2.1.0 -> 2.2.0
Date: Wed, 11 Apr 2018 08:56:02 +0200 [thread overview]
Message-ID: <1681396.WmAqkBQZN7@ada> (raw)
In-Reply-To: <ed728349-7e3e-f391-970b-915ff9aae0a8@pengutronix.de>
Hei hei,
Am Dienstag, 10. April 2018, 17:34:09 CEST schrieb Bastian Stender:
> There are patches on top of htop 2.1.0. You should port them or drop
> them as needed.
FWIW …
0001-linux-LinuxProcessList-fix-reading-of-number-of-read.patch was applied
upstream.
0002-configure-check-for-ncurses-with-ncurses6-config.patch applies cleanly to
htop 2.2.0, but I'm not sure it's needed, they changed ncurses CFLAGS use in
upstream commit bc5d46982f3504000567e00f59e4f7a5905597a9, maybe more info on
that in #695 [1] and #745 [2]. Also they fixed things with pkg-config, so I'm
not sure if it is really needed anymore. Maybe see the discussions about
ncurses6 earlier this year on this list or the commit introducing that patch
(74ffd1f57d0d68a89183ea2bf47c0cd67a989520).
HTH & Greets
Alex
[1] https://github.com/hishamhm/htop/issues/695
[2] https://github.com/hishamhm/htop/pull/745
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-04-11 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 15:14 Roland Hieber
2018-04-10 15:34 ` Bastian Stender
2018-04-11 6:56 ` Alexander Dahl [this message]
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
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=1681396.WmAqkBQZN7@ada \
--to=ada@thorsis.com \
--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