From: Stefan Hajnoczi <stefanha@gmail.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: Require at least spice-protocol-0.12.3
Date: Mon, 4 Mar 2013 11:51:36 +0100 [thread overview]
Message-ID: <20130304105136.GA2837@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <302ae9628718b0c4ae10528ec97e88a6000b6099.1362123798.git.mprivozn@redhat.com>
On Fri, Mar 01, 2013 at 08:43:18AM +0100, Michal Privoznik wrote:
> As of 5a49d3e9 we assume SPICE_PORT_EVENT_BREAK to be defined.
> However, it is defined not in 0.12.2 what we require now, but in
> 0.12.3. Therefore in order to prevent build failure we must
> adjust our minimal requirements.
> ---
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, applied to the trivial patches tree:
https://github.com/stefanha/qemu/commits/trivial-patches
Stefan
prev parent reply other threads:[~2013-03-04 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 7:43 [Qemu-devel] [PATCH] configure: Require at least spice-protocol-0.12.3 Michal Privoznik
2013-03-04 10:51 ` Stefan Hajnoczi [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=20130304105136.GA2837@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).