From: Naphtali Sprei <nsprei@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v2 0/4] block: more read-only changes, related to backing files
Date: Thu, 04 Feb 2010 16:08:58 +0200 [thread overview]
Message-ID: <4B6AD4FA.9090207@redhat.com> (raw)
In-Reply-To: <1265291041-31100-1-git-send-email-nsprei@redhat.com>
Naphtali Sprei wrote:
> This is version 2. The change between previous patch (only 3/4) is the order of closing/re-opening the image.
Sorry,
patch sent without the change of version 2 (in 3/4).
Will send later.
Naphtali
prev parent reply other threads:[~2010-02-04 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 13:43 [Qemu-devel] [PATCH v2 0/4] block: more read-only changes, related to backing files Naphtali Sprei
2010-02-04 13:43 ` [Qemu-devel] [PATCH v2 1/4] Add open_flags to BlockDriverState Will be used later Naphtali Sprei
2010-02-04 13:43 ` [Qemu-devel] [PATCH v2 2/4] qemu-img: Fix qemu-img can't create qcow image based on read-only image Naphtali Sprei
2010-02-04 14:08 ` Naphtali Sprei [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=4B6AD4FA.9090207@redhat.com \
--to=nsprei@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).