From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] The development tree is now open!
Date: Wed, 06 Jun 2012 14:37:20 +0300 [thread overview]
Message-ID: <4FCF40F0.8050201@redhat.com> (raw)
In-Reply-To: <4FCE0772.7010302@siemens.com>
On 06/05/2012 04:19 PM, Jan Kiszka wrote:
>>
>> Note, I am holding off on the qemu-kvm-1.1 release pending investigation
>> of the qcow2/ide bug that Yongjie Ren discovered. But if it's holding
>> you off, I can branch 1.1 now and merge this early to master.
>
> I'm optimistic that the pull I sent yesterday should still merge cleanly
> into a master that contains some qcow2 or whatever fix.
>
That wasn't the issue, rather if we branch now I have to work the fix
into both trees. But I'll stop being lazy and pull.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-06-06 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 9:53 [Qemu-devel] The development tree is now open! Anthony Liguori
2012-06-03 17:05 ` Jan Kiszka
2012-06-05 13:07 ` Avi Kivity
2012-06-05 13:19 ` Jan Kiszka
2012-06-06 11:37 ` Avi Kivity [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=4FCF40F0.8050201@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=mtosatti@redhat.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).