From: Jamie Lokier <jamie@shareable.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] More qcow2 bugs? - qemu-img convert/commit
Date: Thu, 10 Sep 2009 13:27:01 +0100 [thread overview]
Message-ID: <20090910122701.GA32178@shareable.org> (raw)
In-Reply-To: <4AA8CAED.2050409@redhat.com>
Kevin Wolf wrote:
> Am 10.09.2009 11:44, schrieb Jamie Lokier:
> > Kevin Wolf wrote:
> >> Actually, first of all, which qemu version are you using?
> >
> >>> The tool I used is qemu-img from kvm-88, which is the most recent
> >>> release on kvm's home page.
> >
> > Dated 12 July 2009.
>
> Sorry, seems I missed the kvm-88 part. The date of the fix I mentioned
> is 19 July 2009, so I assume your problem is already fixed with current
> git master.
It looks like the right fix, and a simple mistake caused the bug.
Thanks,
-- Jamie
next prev parent reply other threads:[~2009-09-10 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 23:26 [Qemu-devel] More qcow2 bugs? - qemu-img convert/commit Jamie Lokier
2009-09-09 23:42 ` [Qemu-devel] " Paolo Bonzini
2009-09-10 8:27 ` [Qemu-devel] " Kevin Wolf
2009-09-10 8:32 ` Kevin Wolf
2009-09-10 9:44 ` Jamie Lokier
2009-09-10 9:46 ` Kevin Wolf
2009-09-10 12:27 ` Jamie Lokier [this message]
2009-09-11 19:28 ` Jamie Lokier
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=20090910122701.GA32178@shareable.org \
--to=jamie@shareable.org \
--cc=kwolf@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).