Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] procps: disable fancy new top output mode
Date: Tue, 10 Feb 2015 20:03:07 -0500	[thread overview]
Message-ID: <20150211010307.GB3150@windriver.com> (raw)
In-Reply-To: <1421866336-17183-1-git-send-email-paul.gortmaker@windriver.com>

[[PATCH] procps: disable fancy new top output mode] On 21/01/2015 (Wed 13:52) Paul Gortmaker wrote:

> General consensus is that the new output format, with the all red
> colour and one line per core is too fugly to be left as the default.
> 
> Use the configure option to switch it back to the sane default that
> we've all become used to seeing for decades.

Ping -- discussion on IRC was in unanimous agreement with the above
assessment; so it seems like we should get this merged.

P.
--

> 
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
>  meta/recipes-extended/procps/procps_3.3.10.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-extended/procps/procps_3.3.10.bb b/meta/recipes-extended/procps/procps_3.3.10.bb
> index d8b04dc204a0..621b6dd5786c 100644
> --- a/meta/recipes-extended/procps/procps_3.3.10.bb
> +++ b/meta/recipes-extended/procps/procps_3.3.10.bb
> @@ -22,7 +22,7 @@ SRC_URI[sha256sum] = "a02e6f98974dfceab79884df902ca3df30b0e9bad6d76aee0fb5dce17f
>  
>  S = "${WORKDIR}/procps-ng-${PV}"
>  
> -EXTRA_OECONF = "--enable-skill"
> +EXTRA_OECONF = "--enable-skill --disable-modern-top"
>  
>  CPPFLAGS += "-I${S}"
>  
> -- 
> 2.2.1
> 


  reply	other threads:[~2015-02-11  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 18:52 [PATCH] procps: disable fancy new top output mode Paul Gortmaker
2015-02-11  1:03 ` Paul Gortmaker [this message]
2015-02-11  1:54   ` Philip Balister

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=20150211010307.GB3150@windriver.com \
    --to=paul.gortmaker@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