public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Tim Bird <tim.bird@am.sony.com>,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list
Date: Mon, 23 Jun 2008 20:19:11 +0200	[thread overview]
Message-ID: <200806232019.11546.vda.linux@googlemail.com> (raw)
In-Reply-To: <20080623174537.GB4756@cs181140183.pp.htv.fi>

On Monday 23 June 2008 19:45, Adrian Bunk wrote:
> Plus the fact that you often get into situations where more options
> mean complex and fragile stuff. Read the Kconfig files under 
> drivers/media/ and check in git all commits to them since 2.6.25 alone, 
> and you'll understand why "add an option for every bit" can result in
> very high ongoing maintainance work required.
> 
> Not everything that is technically possible is also maintainable, and 
> maintainability is a very important point in a project with several 
> million lines changing each year.

Well, I am not (and was not) disputing this. I agree with it.
CONFIGs should not be multiplying like rabbits.
--
vda

  reply	other threads:[~2008-06-23 18:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 17:42 [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list David Woodhouse
2008-04-30 17:44 ` [PATCH 1/1] " David Woodhouse
2008-05-01  9:55   ` Bart Van Assche
2008-05-01 10:05     ` David Woodhouse
2008-05-01 11:12       ` Bart Van Assche
2008-04-30 18:22 ` [PATCH 0/1] " Andi Kleen
2008-04-30 19:11   ` David Woodhouse
2008-06-23 17:22     ` Denys Vlasenko
2008-06-23 18:57       ` Sam Ravnborg
2008-06-23 19:12         ` Denys Vlasenko
2008-06-23 19:33           ` Sam Ravnborg
     [not found]   ` <48190B5F.9010505@am.sony.com>
     [not found]     ` <20080501095822.GL20451@one.firstfloor.org>
2008-05-01 10:02       ` David Woodhouse
2008-05-01 10:41         ` Andi Kleen
2008-05-02 15:00           ` Pekka Enberg
2008-05-02 20:01             ` Eduard - Gabriel Munteanu
2008-05-02 20:14               ` Andrew Morton
2008-05-02 20:33                 ` Eduard - Gabriel Munteanu
2008-05-02 20:53                   ` Andrew Morton
2008-05-03 22:24                     ` Randy Dunlap
2008-05-05  1:52                       ` Andrew Morton
2008-06-23 17:28           ` Denys Vlasenko
2008-06-23 17:45             ` Adrian Bunk
2008-06-23 18:19               ` Denys Vlasenko [this message]
2008-06-23 19:05               ` Tim Bird
2008-06-25  9:50               ` James Chapman
2008-06-25 15:41                 ` Adrian Bunk
2008-04-30 18:26 ` Josh Boyer
2008-04-30 18:43   ` David Woodhouse
2008-04-30 18:45     ` Josh Boyer
2008-04-30 23:34 ` Adrian Bunk
2008-05-01  7:04   ` David Woodhouse
2008-05-02 11:58 ` Kristoffer Ericson

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=200806232019.11546.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=bunk@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=tim.bird@am.sony.com \
    --cc=torvalds@linux-foundation.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