Dave Jones wrote:
>On Tue, Nov 05, 2002 at 12:08:33PM -0500, Jeff Garzik wrote:
>
> > >Can it really be that one cannot edit a config file and run make
> > >oldconfig anymore? I'm used to editing an entry in .config and running
> > >oldconfig to fix things up, now it just reenables the option. That's
> > >clearly a major regression.
> > >
> > It works fine for me :)
> > I don't think I could survive without the tried and true "vi .config ;
> > make oldconfig" kernel configurator :)
>
>Here it seems to work fine if I delete a line completely, but
>if I change
>CONFIG_FOO=y
>to
>#CONFIG_FOO=y
>
>it regenerates .config without the #
>This used to work fine. I guess the new parser
>is a little more strict..
>
>
well, consider too that '# blah blah' was never really a
completely-free-to-use namespace, it was considered special due to the
shell-based parsing that needed to occur. '# CONFIG_FOO is not set' is
the classic example of using the '#' space...
Jeff
-
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/
This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:38 EST