All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] run make defconfig
Date: Mon, 07 Dec 2009 11:19:26 -0600	[thread overview]
Message-ID: <4B1D391E.9060809@codemonkey.ws> (raw)
In-Reply-To: <20091207094240.GB31370@redhat.com>

Michael S. Tsirkin wrote:
> OK, I got the "Run make defconfig" message again.
> I think it used to be re-run automatically: why
> are we asking the user to do it manually now?
>   
It's buggy.  defconfig should only be needed when a new config option is 
added and the old config doesn't contain it yet.

But we get this message often when a new config option has not been 
added.  I suspect it has something to do with checks on accessed time 
against configure and config*.  We probably need to be smarter than that.

Regards,

Anthony Liguori

  reply	other threads:[~2009-12-07 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  9:42 [Qemu-devel] run make defconfig Michael S. Tsirkin
2009-12-07 17:19 ` Anthony Liguori [this message]
2009-12-07 19:22   ` [Qemu-devel] " Michael S. Tsirkin

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=4B1D391E.9060809@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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.