public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Rob Landley <rob@landley.net>
Cc: Jan Engelhardt <jengelh@computergmbh.de>, linux-kernel@vger.kernel.org
Subject: kconfig/kbuild rewite (Re: What's up with CONFIG_BLK_DEV?)
Date: Sun, 2 Sep 2007 02:02:37 +0200	[thread overview]
Message-ID: <E1IRcvF-0007yi-73@flower> (raw)
In-Reply-To: <200708260108.28584.rob@landley.net>

* Sun, 26 Aug 2007 01:08:28 -0500
* Organization: Boundaries Unlimited
>
[]
> Also "here's a symbol, show me a menu containing everything else that is 
> either required by or enabled by this symbol..."  That sounds like a more 
> powerful abstraction, since the previous one is "show me everything that 
> depends on CONFIG_BLOCK".
>
> (I wonder if this would be a largeish rewrite of the menuconfig 
> infrastructure?  Hmmm...)

Yess. I'm doing this, actually. Sam, Andrew and Linus have got an email
half a year ago about my intent. Tried to release 2.6.20-j4f, but that
was just a dream. Now i did some training in non-kernel related stuff and
always catch (30k, 14k) LKML backlogs to stay in tune. Some bits i 
get are here ftp://flower.upol.cz/Linux/info-LKML/tools/

So, ideas: UI, organization, efficiency, simplicity, etc. are welcome.

Maybe in one month i'll get something to show (base is 2.6.22).
Imagination plays very well, the thing must be ground shaking, but i'll
see how it will fit reality. Yours one in consideration from very
beginning, don't bother :)

Another problem that i have to solve before any publishing (it's
completely another tree, logic, interface), is the work tracking system,
i was describing in June. This is important, because i sick of current
chaos and manual organizing work in-tree or in regression tracking.
____

  parent reply	other threads:[~2007-09-01 23:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 20:17 What's up with CONFIG_BLK_DEV? Rob Landley
2007-08-24 20:34 ` Jan Engelhardt
2007-08-24 20:36   ` Jan Engelhardt
2007-08-26  6:08     ` Rob Landley
2007-08-26  7:41       ` Jan Engelhardt
2007-09-02  0:02       ` Oleg Verych [this message]
2007-09-02 11:51         ` kconfig/kbuild rewite (Re: What's up with CONFIG_BLK_DEV?) Sam Ravnborg
2007-09-03 21:48           ` Oleg Verych
2007-09-04  5:01           ` Rob Landley

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=E1IRcvF-0007yi-73@flower \
    --to=olecom@flower.upol.cz \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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