Messages in this thread | | | Date | Mon, 10 Apr 2006 00:51:53 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH 0/19] kconfig patches |
| |
Roman Zippel <zippel@linux-m68k.org> wrote: > > Hi, > > On Sun, 9 Apr 2006, Andrew Morton wrote: > > > > Andrew, what might be very interesting for you is that kconfig is not > > > rewriting .config anymore all the time by itself and if you set > > > KCONFIG_NOSILENTUPDATE you can even omit the silent updates, so unless you > > > explicitly call one of the config targets, you can be sure kbuild won't > > > touch your .config symlink anymore and as long as the .config is in sync > > > with the Kconfig files you shouldn't see a difference. I'm very interested > > > how that works for you. > > > > Badly, sorry. `make oldconfig' blows away the .config symlink. > > I know, that's why I said "unless you explicitly call one of the config > targets",
I know that's why you said that ;)
> If you call "make oldconfig", you have to restore the symlink manually.
Why? What advantage does that have?
I've been using the copy-it-there approach for maybe four years and have yet to notice any problem with it.
- 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/
| |