From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, "Avi Kivity" <avi@redhat.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Mike Galbraith" <efault@gmx.de>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Paul Mackerras" <paulus@samba.org>
Subject: Re: [PATCH 6/6] perf report: Initial TUI using newt
Date: Thu, 11 Mar 2010 19:15:29 -0300 [thread overview]
Message-ID: <20100311221529.GM14180@ghostprotocols.net> (raw)
In-Reply-To: <1268345617-31863-6-git-send-email-acme@infradead.org>
Em Thu, Mar 11, 2010 at 07:13:37PM -0300, Arnaldo Carvalho de Melo escreveu:
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Newt has widespread availability and provides a rather simple API as can be
> seen by the size of this patch.
>
> The work needed to support it will benefit other frontends too.
>
> In this initial patch it just checks if the output is a tty, if not it falls
> back to the previous behaviour, also if newt-devel/libnewt-dev is not installed
> the previous behaviour is maintaned.
Argh, please don't consider this last patch (6/6), I messed up, will
repost just this one in a few moments.
- Arnaldo
next prev parent reply other threads:[~2010-03-11 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 22:13 [PATCH 1/6] perf symbols: Bump plt synthesizing warning debug level Arnaldo Carvalho de Melo
2010-03-11 22:13 ` [PATCH 2/6] perf top: Export get_window_dimensions Arnaldo Carvalho de Melo
2010-03-11 22:13 ` [PATCH 3/6] perf tools: Use eprintf for pr_{err,warning,info} too Arnaldo Carvalho de Melo
2010-03-11 22:13 ` [PATCH 4/6] perf report: Initial TUI using newt Arnaldo Carvalho de Melo
2010-03-11 22:13 ` [PATCH 5/6] perf tools: Add missing bytes printed in hist_entry__fprintf Arnaldo Carvalho de Melo
2010-03-11 22:13 ` [PATCH 6/6] perf report: Initial TUI using newt Arnaldo Carvalho de Melo
2010-03-11 22:15 ` Arnaldo Carvalho de Melo [this message]
2010-03-11 22:22 ` Arnaldo Carvalho de Melo
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=20100311221529.GM14180@ghostprotocols.net \
--to=acme@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.