I'm finding this report very puzzling. Both front ends parse the
.config in exactly the same order. In fact, it's done by the same
> Suggestion: On the first pass of CML2 processing through .config, before
> first config.out created, trust the top level setting and ignore lower level
> settings if top setting off.
Because of the order tree traversal is done, I think ttyconfig should give
you the effect you want.
> 2. So after some playing around, I want to go back to CML1. But the .config
> generated by CML2 is not compatible. I don't know if it's supposed to be
> but there's lots of problems.
The config.out isn't exactly compatible; it has explicit CONFIG_FOO=n settings
in it. The .config file generated from that by configtrans should be, however;
if it's not that's a bug. Can you send me your "incompatible" .config so
I can see the problems?
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Never trust a man who praises compassion while pointing a gun at you. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/