From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>"
<7eggert@gmx.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Jesper Juhl <juhl-lkml@dif.dk>
Subject: Re: [kbuild-devel] Re: [2.6 patch] Kconfig: rename "---help---" to "help" in Kconfig files (first part)
Date: Wed, 4 May 2005 06:54:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0505040651400.6658@localhost.localdomain> (raw)
In-Reply-To: <E1DSxtF-0001Dz-N6@be1.7eggert.dyndns.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1057 bytes --]
On Tue, 3 May 2005, Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org> wrote:
> Roman Zippel <zippel@linux-m68k.org> wrote:
> > On Tue, 3 May 2005, Adrian Bunk wrote:
>
> >> IMHO, Kconfig files are quite readable due to this indentation even
> >> though only a minority of the entries was using "---help---" even
> >> before this patch.
> >
> > So why exactly has to be removed? Is it ugly?
>
> IMO yes, it's less readable for me than "help". ¢¢
the main problem with having two alternatives for the same thing (in
*any* context) is that it gives beginners a distorted sense of what is
acceptable usage.
if you accept both "help" and "---help---", then you just *know* that
a beginner will notice that and start thinking, "hmmm ... well, if
both of those are alright, maybe "--help--" or "-help-" is alright,
too. and maybe it's just the leading hyphens that really count, not
the trailing hyphens. and maybe ..."
kbuild is already over-convoluted as it is. please don't give folks
even more redundant ways to do exactly the same thing.
rday
prev parent reply other threads:[~2005-05-04 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ZTLT-3D3-1@gated-at.bofh.it>
[not found] ` <401Js-1AH-1@gated-at.bofh.it>
[not found] ` <401Tf-1Hp-9@gated-at.bofh.it>
[not found] ` <402FB-2mN-15@gated-at.bofh.it>
2005-05-03 13:56 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-05-04 10:54 ` Robert P. J. Day [this message]
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=Pine.LNX.4.61.0505040651400.6658@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=juhl-lkml@dif.dk \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®