AW: [RFC] KConfig merge

[Maksim Orlovich]

> Hello
> We tried very hard, but we couldn't get this ready for today.
> The main problem is, that the header structure of the config classes is
> now
> much clearer, which (they now only the things in the really nead, which is
> much less hen before)

Is there any reason other than pedantism to not make them backwards
compatible, and avoid porting? We're supposed to be stabilizing here.