From: Fam Zheng <famcool@gmail.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, Fam Zheng <famcool@gmail.com>,
hch@lst.de, stefanha@gmail.com
Subject: [Qemu-devel] [PATCH v3 0/8] Add various VMDK subformats support
Date: Fri, 12 Aug 2011 23:19:26 +0800 [thread overview]
Message-ID: <1313162374-13147-1-git-send-email-famcool@gmail.com> (raw)
Changes:
02/06: Free extents on fail in vmdk_open.
Added:
07/08: VMDK: bugfix, open Haiku vmdk image
08/08: VMDK: bugfix, opening vSphere 4 exported image
Fam Zheng (8):
VMDK: enable twoGbMaxExtentFlat
VMDK: add twoGbMaxExtentSparse support
VMDK: separate vmdk_read_extent/vmdk_write_extent
VMDK: Opening compressed extent.
VMDK: read/write compressed extent
VMDK: creating streamOptimized subformat
VMDK: bugfix, open Haiku vmdk image
VMDK: bugfix, opening vSphere 4 exported image
block/vmdk.c | 346 +++++++++++++++++++++++++++++++++++++++++++++-------------
1 files changed, 270 insertions(+), 76 deletions(-)
next reply other threads:[~2011-08-12 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 15:19 Fam Zheng [this message]
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 1/8] VMDK: enable twoGbMaxExtentFlat Fam Zheng
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 2/8] VMDK: add twoGbMaxExtentSparse support Fam Zheng
2011-09-06 10:38 ` Kevin Wolf
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 3/8] VMDK: separate vmdk_read_extent/vmdk_write_extent Fam Zheng
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 4/8] VMDK: Opening compressed extent Fam Zheng
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 5/8] VMDK: read/write " Fam Zheng
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 6/8] VMDK: creating streamOptimized subformat Fam Zheng
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 7/8] VMDK: bugfix, open Haiku vmdk image Fam Zheng
2011-08-12 15:19 ` [Qemu-devel] [PATCH v3 8/8] VMDK: bugfix, opening vSphere 4 exported image Fam Zheng
2011-09-05 8:15 ` [Qemu-devel] [PATCH v3 0/8] Add various VMDK subformats support Stefan Hajnoczi
2011-09-06 10:40 ` Kevin Wolf
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=1313162374-13147-1-git-send-email-famcool@gmail.com \
--to=famcool@gmail.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).