On Sat, Sep 15, 2007 at 11:44:59AM -0400, Jeff Garzik wrote:I doubt your claim is true since the vast majority of kconfig users are most likely not kernel developers. @Greg: Do you have any numbers regarding how your "Linux Kernel in a Nutshell" is selling? Even download numbers? It's not only about switching, the same problems awaits people when configuring a kernel for their hardware the first time. Why don't we dump kconfig and write the .config by hand? ;-) More seriously: Yes, there are many other important issues in the kernel. But not fixing kconfig UI problems doesn't fix these issues faster. I have seen people running into problems because some required option wasn't set - in the simplest cases things like IDE without DMA because a help text wasn't updated when more hardware support was added to a driver. You might not care about the kconfig users. But other people do. 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 -
| Christoph Lameter | Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Pekka Enberg | Re: [bug] mm/slab.c boot crash in -git, "kernel BUG at mm/slab.c:2103!" |
| Glauber de Oliveira Costa | [PATCH 08/79] [PATCH] use identify_boot_cpu |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| David Miller | [GIT]: Networking |
