All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	"Elyse M. Grasso" <emgrasso@data-raptors.com>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	kbuild-devel@lists.sourceforge.net,
	Andreas Herrmann <aherrman@arcor.de>
Subject: Re: A bit of kconfig rewrite (Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL)
Date: Sat, 6 Oct 2007 19:51:45 +0200	[thread overview]
Message-ID: <20071006175145.GD22435@flower.upol.cz> (raw)
In-Reply-To: <alpine.LFD.0.999.0710060900040.23684@woody.linux-foundation.org>

On Sat, Oct 06, 2007 at 09:03:00AM -0700, Linus Torvalds wrote:
> 
> 
> On Sat, 6 Oct 2007, Oleg Verych wrote:
> > 
> > Thanks. I will be specific, after i will finish, what i already have,
> > to make air a bit less hot. Of course everything will be back
> > compatible, so nothing to worry about (the rewrite).
> 
> Qutie frankly, this kind of "I'll tell you more when I'm done" is not 
> generally a very working approach. 
> 
> If it's all backwards-compatible with the current Kconfig format, I guess 
> it's not too bad, but historically speaking, the people who went off on 
> their own and redesigned something from scratch have not been successful 
> (and the CML2 thing is a good example of that).

Spent whole September on LKML archive (grave) digging, actually. So,
please, get me right.

If i have finally made statement like that (rewrite with new design),
that basically means, i'll try to bring something, that probably will be
better, not emotionally (CML2 :), but technically (kbuild-2.5's 100%
slowdown of some important functionality :).

> Incremental improvements actually tend to do better than "redesign".  

I'm not going to call (and thus targeting) that thing "kbuild-2.7" or
"kconfig-ng", "CML3000" or anything like that.

If my proposal will fit, i.e. configuring and building something
(anything) becomes more easy, more flexible, etc., then any project can
try and adopt it actually. And this will be a measure of quality.

> That's largely true outside of computer science too..

Will see. If i will fail, who will care; i will not. Somebody spend years
of doing that, what was rejected. More than 5 years of current
kbuild/kconfig "development calmness". So...

Maintenance and acceptance of the m4/make/perl/C/ncurses community of my
mainly `TERM=linux ; sed && sh' approach is more important for me.

Thanks, Linus.
____

  reply	other threads:[~2007-10-06 17:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18  8:05 [PATCH] 9p: fix compile error if !CONFIG_SYSCTL Andreas Herrmann
2007-09-18 18:53 ` roel
2007-09-18 20:15   ` Andreas Herrmann
2007-09-20  6:31 ` Andrew Morton
2007-09-20  7:23   ` Andreas Herrmann
2007-09-27 21:40   ` Nick Piggin
2007-09-28 14:34     ` Linus Torvalds
2007-09-28  0:05       ` Nick Piggin
2007-09-28 17:11         ` Arjan van de Ven
2007-09-28 17:12         ` Elyse M. Grasso
2007-10-01  7:27           ` A bit of kconfig rewrite (Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL) Oleg Verych
2007-10-01  8:05             ` Sam Ravnborg
2007-10-01 12:53             ` Elyse M. Grasso
2007-10-05  2:35             ` [kbuild-devel] " Roman Zippel
2007-10-06 15:26               ` Oleg Verych
2007-10-06 16:03                 ` Linus Torvalds
2007-10-06 17:51                   ` Oleg Verych [this message]
2007-10-06 18:59                     ` Sam Ravnborg
2007-10-06 20:47                       ` Oleg Verych
2007-10-06 21:10                         ` Sam Ravnborg
2007-10-06 22:07                           ` Oleg Verych
2007-10-07  9:49                             ` Geert Uytterhoeven
2007-10-08 20:22                             ` Sam Ravnborg
2007-10-08 21:25                               ` Oleg Verych

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=20071006175145.GD22435@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=aherrman@arcor.de \
    --cc=akpm@linux-foundation.org \
    --cc=emgrasso@data-raptors.com \
    --cc=ericvh@gmail.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.