From: Blue Swirl <blauwirbel@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Document qemu-img create -o
Date: Sat, 6 Jun 2009 18:45:12 +0300 [thread overview]
Message-ID: <f43fc5580906060845g71b257dctf996ee08b5a8ed17@mail.gmail.com> (raw)
In-Reply-To: <1244122779-32728-1-git-send-email-kwolf@redhat.com>
On 6/4/09, Kevin Wolf <kwolf@redhat.com> wrote:
> 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.
Thanks, applied.
With hxtool the documentation and code could be kept in one place...
prev parent reply other threads:[~2009-06-06 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 13:39 [Qemu-devel] [PATCH 0/2] Document qemu-img create -o Kevin Wolf
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 ` Blue Swirl [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=f43fc5580906060845g71b257dctf996ee08b5a8ed17@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).