From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH v2] Force object directory use
Date: Wed, 17 Nov 2010 23:39:52 +0100 [thread overview]
Message-ID: <4CE459B8.7050204@redhat.com> (raw)
In-Reply-To: <AANLkTimnrn0xi=EGj+h_gHrA_bYSU=MKwV0=jNyhaMB2@mail.gmail.com>
On 11/17/2010 09:08 PM, Blue Swirl wrote:
> It's not simplification but to unify the build system. Some people
> make changes to Makefiles and then test their changes without an
> object directory, these may then break the build for those who use it.
> This has happened several times already. Hopefully we can avoid those
> breakages with this change.
It happens very rarely, and the last time it was because the wrong patch
was committed IIUC. It may be unified but it's pretty much unlike every
other build system I've ever seen.
Paolo
next prev parent reply other threads:[~2010-11-17 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 19:15 [Qemu-devel] [PATCH v2] Force object directory use Blue Swirl
2010-11-17 20:00 ` [Qemu-devel] " Paolo Bonzini
2010-11-17 20:08 ` Blue Swirl
2010-11-17 22:39 ` Paolo Bonzini [this message]
2010-11-17 23:05 ` Peter Maydell
2010-11-17 23:51 ` Paolo Bonzini
2010-11-17 23:57 ` Anthony Liguori
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=4CE459B8.7050204@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).