From: Adrian Bunk <bunk@stusta.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: 2.6.22-git* regression: Kconfig prompts without help text
Date: Wed, 18 Jul 2007 20:37:27 +0200 [thread overview]
Message-ID: <20070718183727.GL3801@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0707182031130.5385@fbirervta.pbzchgretzou.qr>
On Wed, Jul 18, 2007 at 08:33:27PM +0200, Jan Engelhardt wrote:
>
> On Jul 18 2007 11:04, Randy Dunlap wrote:
> >> > I have no idea where it came from. (not me)
> >>
> >> It was akpm:
> >> http://linux.bkbits.net:8080/linux-2.6/Documentation/CodingStyle?PAGE=diffs&REV=1.5
> >
> > I think that would only make sense if "---help---" is used (like you did)
> > instead of the plain "help" string.
> >
> > In the case of "---help---", it's OK with me not to be indented by 2 more
> > spaces.
>
> ===
>
> kconf also accepts "---help---" besides the usual "help" keyword.
> If it is used, I think we can omit the extra spaces, because the
> dashes are visible enough a sash.
Nope, the majority of "---help---" users don't omit the spaces - and it's
more readable with them.
> Signed-off-by: Jan Engelhardt <jengelh@gmx.de>
>
> ---
> Documentation/CodingStyle | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> Index: linux-2.6.23/Documentation/CodingStyle
> ===================================================================
> --- linux-2.6.23.orig/Documentation/CodingStyle
> +++ linux-2.6.23/Documentation/CodingStyle
> @@ -511,17 +511,16 @@ remember: "indent" is not a fix for bad
>
> For all of the Kconfig* configuration files throughout the source tree,
> the indentation is somewhat different. Lines under a "config" definition
> -are indented with one tab, while help text is indented an additional two
> -spaces. Example:
> +are indented with one tab. Example:
>
> config AUDIT
> bool "Auditing support"
> depends on NET
> - help
> - Enable auditing infrastructure that can be used with another
> - kernel subsystem, such as SELinux (which requires this for
> - logging of avc messages output). Does not do system-call
> - auditing without CONFIG_AUDITSYSCALL.
> + ---help---
> + Enable auditing infrastructure that can be used with another
> + kernel subsystem, such as SELinux (which requires this for
> + logging of avc messages output). Does not do system-call
> + auditing without CONFIG_AUDITSYSCALL.
>
> Features that might still be considered unstable should be defined as
> dependent on "EXPERIMENTAL":
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-07-18 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 18:49 2.6.22-git* regression: Kconfig prompts without help text Stefan Richter
2007-07-18 15:18 ` Jan Engelhardt
2007-07-18 16:00 ` Stefan Richter
2007-07-18 16:41 ` Randy Dunlap
2007-07-18 17:17 ` Jan Engelhardt
2007-07-18 17:34 ` Randy Dunlap
2007-07-18 17:55 ` Jan Engelhardt
2007-07-18 18:04 ` Randy Dunlap
2007-07-18 18:33 ` Jan Engelhardt
2007-07-18 18:37 ` Adrian Bunk [this message]
2007-07-19 20:26 ` Geert Uytterhoeven
2007-07-19 20:49 ` Stefan Richter
2007-07-19 21:05 ` Geert Uytterhoeven
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=20070718183727.GL3801@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=stefanr@s5r6.in-berlin.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