[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1IRcvF-0007yi-73@flower>
Date: Sun, 2 Sep 2007 02:02:37 +0200
From: Oleg Verych <olecom@...wer.upol.cz>
To: Rob Landley <rob@...dley.net>
Cc: Jan Engelhardt <jengelh@...putergmbh.de>,
linux-kernel@...r.kernel.org
Subject: kconfig/kbuild rewite (Re: What's up with CONFIG_BLK_DEV?)
* 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.
____
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists