* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > On Fri, 21 Aug 2009, Ingo Molnar wrote: > > > > > * Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > > On Thu, 20 Aug 2009 17:43:38 -0400 (EDT) > > > Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > > > > > > > > > > > > > The following patches are in: > > > > > > > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git > > > > > > > > > > > > branch: kconfig > > > > > > > > > > Sam's been quiet lately. I suggest that you add this to linux-next > > > > > now so people get a chance to poke at it. > > > > > > > > I have no means of pushing into next. Would someone like to do a pull for > > > > me? > > > > > > If suitably bribed, Stephen will add you tree directly to the > > > linux-nxt lineup. > > > > Yep, we always needed another kconfig maintainer (Sam's being mostly > > busy with kbuild), and it's nice to see that Steve volunteered for > > that job now! ;-) > > Sure why not? > > I've created a new repo: > > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-kconfig.git > > and the same changes are in the branch: for-next Cool! I'm wondering, what do you think about Vegard's 'warn about complex selects' feature for kconfig which he submitted some time ago: http://lkml.org/lkml/2008/5/4/13 That's a really sore kconfig spot we have. It's not a bug, but it sure bites people again and again, and it would be nice to have some built-in mechanism that gently nudges us away from complex selects. (many of which are inadvertent or become complex after the fact) Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
