qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v5] pci, pc, virtio fixes and cleanups
Date: Sat, 7 Mar 2015 18:51:25 +0100	[thread overview]
Message-ID: <20150307175125.GB30667@redhat.com> (raw)
In-Reply-To: <CAFEAcA8xpjpFGt2Rm8cynBZsxUO5eNtRPEbH8n=YDbdxCsXYWg@mail.gmail.com>

On Fri, Mar 06, 2015 at 11:37:49PM +0900, Peter Maydell wrote:
> On 6 March 2015 at 23:27, Markus Armbruster <armbru@redhat.com> wrote:
> > It looks like we now generate a bunch of files that used to be
> > git-controlled.  The "generate" part is fine.  But generating into the
> > source tree is asking for trouble.
> >
> > What happens when I build separate build trees in parallel?
> >
> > Why is it a good idea to generate into the source tree instead of the
> > build tree?
> 
> That sounds like a bug to me...
> 
> -- PMM

I just switched between master and my pull several times
without ill effects.

  parent reply	other threads:[~2015-03-07 17:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 15:10 [Qemu-devel] [PULL v5] pci, pc, virtio fixes and cleanups Michael S. Tsirkin
2015-03-06 14:27 ` Markus Armbruster
2015-03-06 14:37   ` Peter Maydell
2015-03-06 14:46     ` Markus Armbruster
2015-03-07 17:51     ` Michael S. Tsirkin [this message]
2015-03-07 18:17     ` Michael S. Tsirkin
2015-03-08  0:15       ` Peter Maydell
2015-03-08 10:45         ` Michael S. Tsirkin
2015-03-08 12:26           ` Peter Maydell
2015-03-08 12:41             ` Michael S. Tsirkin
2015-03-06 15:02   ` Igor Mammedov
2015-03-06 16:15     ` Markus Armbruster
2015-03-07 18:00       ` Michael S. Tsirkin
2015-03-07 17:49   ` 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=20150307175125.GB30667@redhat.com \
    --to=mst@redhat.com \
    --cc=armbru@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).