Having thought about this a little more, I don't think it's correct. It's
cute and I still love the idea of forcing people to document - I sometimes
imagine there exist contributors who make a point of not documenting - but
the need for a clean design with as few corner cases as possible trumps that.
Suppose I'm working on my patch, doing the part that hooks into config. It
works, I can see my new feature, but for some strange reason the buttons are
grayed out. After I fiddle a while I clue in to the idea that the
'experimental' setting might have something to do with it, I turn it on and
then my buttons work. Now, what the? Eventually I figure out this is
supposed to be a feature, not a bug, and that including some help will
activate my buttons. So I curse the author up and down and submit a patch to
remove that feature.
This is a admittedly a small point and I'm not going to quibble about it any
more. I'm happy the kbuild process is being cleaned up. I've wasted too
much time due to shortcomings in the old one.
I'll wait until this gets into the tree before submitting my patch ;-)
-- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/