From: Adrian Bunk <bunk@stusta.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Jesper Juhl <juhl-lkml@dif.dk>
Subject: Re: [2.6 patch] Kconfig: rename "---help---" to "help" in Kconfig files (first part) (fwd)
Date: Tue, 31 May 2005 02:41:20 +0200 [thread overview]
Message-ID: <20050531004120.GH3627@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0505310217030.3728@scrub.home>
On Tue, May 31, 2005 at 02:17:50AM +0200, Roman Zippel wrote:
> Hi,
Hi Roman,
> On Tue, 31 May 2005, Adrian Bunk wrote:
>
> > The main reason for this patch (quoting Jesper) is:
> > Consistency. out of ~4000 help entries in 134 Kconfig files, 747 of
> > those entries use "---help---" as the keyword, the rest use just "help".
> > So the users of "---help---" are clearly a minority and by renaming them
> > we make things consistent. - I hate inconsistency. :-)
>
> And I still don't like this change...
there's still the point that it's currently used inconsistently.
If you really prefer "---help---" over "help" (I consider "help" being
better, but as long as it's used consistently each of them is
acceptable), feel free to send a patch instead that changes all
occurences of "help" to "---help---".
> bye, Roman
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:[~2005-05-31 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 0:10 [2.6 patch] Kconfig: rename "---help---" to "help" in Kconfig files (first part) (fwd) Adrian Bunk
2005-05-31 0:17 ` Roman Zippel
2005-05-31 0:41 ` Adrian Bunk [this message]
2005-05-31 11:16 ` Roman Zippel
2005-05-31 17:28 ` Jesper Juhl
2005-05-31 17:46 ` randy_dunlap
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=20050531004120.GH3627@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--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