public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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)
Date: Wed, 4 May 2005 13:50:24 +0200	[thread overview]
Message-ID: <20050504115024.GM3592@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0505031519310.996@scrub.home>

On Tue, May 03, 2005 at 03:47:46PM +0200, Roman Zippel wrote:

> Hi,

Hi Roman,

> On Tue, 3 May 2005, Adrian Bunk wrote:
> 
> > > So why exactly has to be removed? Is it ugly? Does it make Kconfig worse?
> > 
> > The ugly thing is that there are currently two different ways to express 
> > the same thing. It only causes confusion for people who think those 
> > different syntaxes had a different meaning.
> 
> Languages often have more than one way to express something, this is not 
> different.
> Early on there was some confusion about this from people writing new 
> Kconfig entries (not just reading existing ones), but this was became a 
> non-issue since it's documented now.
>...

Different ways for expressing the same thing is good for writers but bad 
for readers.

E.g. where to place opening braces in C is a religious issue. For the 
Linux kernel, CodingStyle sets the rules. And although I'd prefer to set 
them different, I have to admit that the consistency indide the kernel 
makes reading easier.

> 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


  reply	other threads:[~2005-05-04 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03  0:34 [2.6 patch] Kconfig: rename "---help---" to "help" in Kconfig files (first part) Adrian Bunk
2005-05-03  9:10 ` Roman Zippel
2005-05-03  9:22   ` Adrian Bunk
2005-05-03 10:09     ` Roman Zippel
2005-05-03 10:57       ` Adrian Bunk
2005-05-03 13:47         ` Roman Zippel
2005-05-04 11:50           ` Adrian Bunk [this message]
     [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>

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=20050504115024.GM3592@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