public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Adrian Bunk <bunk@kernel.org>,
	Josh Boyer <jwboyer@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: Kconfig no longer outputs a .config with freshly updated defconfigs
Date: Tue, 5 Aug 2008 22:43:32 +0200	[thread overview]
Message-ID: <20080805204332.GB5464@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0808050435320.6791@localhost.localdomain>

On Tue, Aug 05, 2008 at 04:50:16AM +0200, Roman Zippel wrote:
> Hi,
> 
> On Mon, 4 Aug 2008, Sam Ravnborg wrote:
> 
> > > Why can't we simply always write the .config?
> > 
> > Hi Adrian.
> > 
> > I just pushed a patch that does this.
> 
> If I see it correctly that's not quite correct either. The old 
> silentoldconfig does a few things differently than a normal config target, 
> because it's a special target called by Kbuild when needed:
> 
> - bail out if input is needed but stdio is not a tty
> - silent mode
> - update .config only as needed
> - always update autoconf
> 
> With the change to make the silent mode the default, the "silent" name has 
> become a little obsolete and should probably be renamed, but whatever the 
> name above actions should still be done if called by Kbuild internally.

silentoldconfig now always update .config - and that a bug.
I was too hasty ghere - sorry.
Will fix it during the weekend.

	Sam

  reply	other threads:[~2008-08-05 20:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1217693013.2328.22.camel@localhost.localdomain>
2008-08-02 19:26 ` Kconfig no longer outputs a .config with freshly updated defconfigs Adrian Bunk
2008-08-02 23:58   ` Josh Boyer
2008-08-03  8:00   ` Sam Ravnborg
2008-08-03 10:07     ` Adrian Bunk
2008-08-04 21:08       ` Sam Ravnborg
2008-08-05  2:50         ` Roman Zippel
2008-08-05 20:43           ` Sam Ravnborg [this message]
2008-08-09  5:26             ` Roman Zippel

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=20080805204332.GB5464@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bunk@kernel.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox