From: Ingo Molnar <mingo@elte.hu>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>, git@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl, paulus@samba.org
Subject: Re: [PATCH v2 0/4] perf bench: Common option for specifying style formatting
Date: Tue, 10 Nov 2009 09:01:35 +0100 [thread overview]
Message-ID: <20091110080135.GA32322@elte.hu> (raw)
In-Reply-To: <20091110.165102.386189748263321818.mitake@dcl.info.waseda.ac.jp>
* Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp> wrote:
> And I have a question.
> In tools/perf/command-list.txt, there is the word "mainporcelain".
> What does this mean?
tools/perf/ inherited the command-list.txt code from the Git project:
git://git.kernel.org/pub/scm/git/git.git
in Git talk, 'porcelain' is the pretty stuff humans use. 'plumbing' is
the lowlevel stuff humans dont get to see.
'mainporcelain' are the major commands you get listed when you type
'perf' (or 'git').
( i've Cc:-ed the Git list as i never saw any real formal definition for
this anywhere, maybe i got this wrong :-)
> Of course I searched this word on my dictionary, but cannot got an answer.
> I'm preparing the initial document for perf-bench.
> Can I add perf-bench with mainporcelain to command-list.txt?
yeah, i'd suggest to do that - that will make 'perf bench' show up in
'perf' output.
Ingo
next prev parent reply other threads:[~2009-11-10 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 23:19 [PATCH v2 0/4] perf bench: Common option for specifying style formatting Hitoshi Mitake
2009-11-09 23:19 ` [PATCH v2 1/4] perf bench: Add stuffs to bench.h for unified output formatting Hitoshi Mitake
2009-11-10 4:22 ` [tip:perf/bench] perf bench: Add format constants " tip-bot for Hitoshi Mitake
2009-11-09 23:20 ` [PATCH v2 2/4] perf bench: Modify builtin-bench.c for processing common options Hitoshi Mitake
2009-11-10 4:22 ` [tip:perf/bench] " tip-bot for Hitoshi Mitake
2009-11-09 23:20 ` [PATCH v2 3/4] perf bench: Modified bench/bench-messaging.c to adopt unified output formatting Hitoshi Mitake
2009-11-10 4:22 ` [tip:perf/bench] perf bench: Modify " tip-bot for Hitoshi Mitake
2009-11-09 23:20 ` [PATCH v2 4/4] perf bench: Modify builtin-pipe.c for processing common options Hitoshi Mitake
2009-11-10 4:22 ` [tip:perf/bench] " tip-bot for Hitoshi Mitake
2009-11-10 3:58 ` [PATCH v2 0/4] perf bench: Common option for specifying style formatting Ingo Molnar
2009-11-10 7:51 ` Hitoshi Mitake
2009-11-10 8:01 ` Ingo Molnar [this message]
2009-11-10 8:23 ` Hitoshi Mitake
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=20091110080135.GA32322@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitake@dcl.info.waseda.ac.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox