All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: [PATCH 0/19] kconfig patches
Date: Mon, 10 Apr 2006 00:51:53 -0700	[thread overview]
Message-ID: <20060410005153.2a5c19e2.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0604101035240.32445@scrub.home>

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.


  reply	other threads:[~2006-04-10  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09 15:26 [PATCH 0/19] kconfig patches Roman Zippel
2006-04-10  6:55 ` Andrew Morton
2006-04-10  8:46   ` Roman Zippel
2006-04-10  7:51     ` Andrew Morton [this message]
2006-04-10  9:35       ` Roman Zippel
2006-04-10  8:41         ` Andrew Morton
2006-04-10 11:36           ` Roman Zippel
2006-04-10 15:22             ` Randy.Dunlap
2006-04-10 21:24             ` Andrew Morton
2006-04-12 10:51               ` Roman Zippel
2006-04-20  3:51 ` Randy.Dunlap
2006-04-26 22:13   ` Roman Zippel
2006-04-26 22:38     ` Randy.Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060410005153.2a5c19e2.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.