From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] Document qemu-img create -o
Date: Thu, 4 Jun 2009 15:39:37 +0200 [thread overview]
Message-ID: <1244122779-32728-1-git-send-email-kwolf@redhat.com> (raw)
The bad habit of implementing things and no letting anybody know what has
hanged... This patch series makes the qemu-img -o option actually usable
without reading the code by documenting things.
Kevin Wolf (2):
qemu-img: Print available options with -o ?
Document changes in qemu-img interface
block/cow.c | 12 ++++++++++--
block/qcow.c | 18 +++++++++++++++---
block/qcow2.c | 30 +++++++++++++++++++++++++-----
block/raw-posix.c | 6 +++++-
block/raw-win32.c | 6 +++++-
block/vmdk.c | 18 +++++++++++++++---
block/vpc.c | 6 +++++-
qemu-img.c | 27 ++++++++++++++++++++-------
qemu-img.texi | 32 ++++++++++++++++++--------------
qemu-option.c | 13 +++++++++++++
qemu-option.h | 2 ++
11 files changed, 133 insertions(+), 37 deletions(-)
next reply other threads:[~2009-06-04 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 13:39 Kevin Wolf [this message]
2009-06-04 13:39 ` [Qemu-devel] [PATCH 1/2] qemu-img: Print available options with -o ? Kevin Wolf
2009-06-04 13:39 ` [Qemu-devel] [PATCH 2/2] Document changes in qemu-img interface Kevin Wolf
2009-06-06 15:45 ` [Qemu-devel] [PATCH 0/2] Document qemu-img create -o Blue Swirl
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=1244122779-32728-1-git-send-email-kwolf@redhat.com \
--to=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).