From: Thomas Renninger <trenn@suse.de>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: cpufreq@vger.kernel.org
Subject: Re: [cpupower] RFC: use man(1) when calling "cpupower help subcommand"
Date: Wed, 10 Aug 2011 08:53:53 +0200 [thread overview]
Message-ID: <201108100853.54106.trenn@suse.de> (raw)
In-Reply-To: <20110806161143.GA12443@comet.dominikbrodowski.net>
On Saturday 06 August 2011 18:11:43 Dominik Brodowski wrote:
> Instead of printing something non-formatted to stdout, call
> man(1) to show the man page for the proper subcommand.
Nice!
> -extern void set_help(void);
> -extern void info_help(void);
> -extern void freq_set_help(void);
> -extern void freq_info_help(void);
> -extern void idle_info_help(void);
> -extern void monitor_help(void);
I wonder whether these are still needed then.
If they can get removed translations, maintenance overhead
(adjusting 2 places when adding a parameter) and the size of the
binaries could get reduced.
Not tested yet, but I'll give it a try later.
Thomas
next prev parent reply other threads:[~2011-08-10 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 16:11 [cpupower] RFC: use man(1) when calling "cpupower help subcommand" Dominik Brodowski
2011-08-10 6:53 ` Thomas Renninger [this message]
2011-08-10 11:28 ` Dominik Brodowski
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=201108100853.54106.trenn@suse.de \
--to=trenn@suse.de \
--cc=cpufreq@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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