From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rules.mak: Also try -r to build modules
Date: Tue, 29 Nov 2016 18:43:42 +0100 [thread overview]
Message-ID: <b1f1dae2-532b-d0c1-f67e-bcb05f8d3e56@redhat.com> (raw)
In-Reply-To: <20161129171656.GA7838@stefanha-x1.localdomain>
On 29/11/2016 18:16, Stefan Hajnoczi wrote:
> FWIW I applied the pull request with the broken -r fix. Then I applied
> this patch on top (and added a note to the commit description explaining
> this was a refinement). I've also merged your newest pull request for
> -rc2.
Ok, that pull request (as expected) is a no-op if you kept v1 in the
tree. I thought you hadn't because you didn't mention fixing the
mini-conflict here.
Paolo
prev parent reply other threads:[~2016-11-29 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 15:37 [Qemu-devel] [PATCH] rules.mak: Also try -r to build modules Paolo Bonzini
2016-11-29 16:22 ` Stefan Hajnoczi
2016-11-29 16:57 ` Paolo Bonzini
2016-11-29 17:16 ` Stefan Hajnoczi
2016-11-29 17:43 ` Paolo Bonzini [this message]
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=b1f1dae2-532b-d0c1-f67e-bcb05f8d3e56@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@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 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).