All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Add qcow2 documentation
Date: Wed, 09 Mar 2011 14:55:47 +0100	[thread overview]
Message-ID: <4D7786E3.9070704@redhat.com> (raw)
In-Reply-To: <AANLkTimUH7PKyK8-9awAiRGpoZv=4ciNt5i4EJLiY1nJ@mail.gmail.com>

Am 09.03.2011 14:08, schrieb Stefan Hajnoczi:
> On Wed, Mar 9, 2011 at 12:30 PM, Kevin Wolf <kwolf@redhat.com> wrote:
>> This adds a description of the qcow2 file format to the docs/ directory.
>> Besides documenting what's there, which is never wrong, the document should
>> provide a good basis for the discussion of format extensions (called "qcow3"
>> in previous discussions)
>>
>> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
>> ---
>>  docs/specs/qcow2.txt |  233 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>  1 files changed, 233 insertions(+), 0 deletions(-)
>>  create mode 100644 docs/specs/qcow2.txt
> 
> QCOW2_EXT_MAGIC_BACKING_FORMAT is not documented.  Did you decide that
> is a QEMU internal extension and you don't want it documented?

I just completely forgot to include header extensions. Though I think
the allowed values for the backing file format are implementation specific.

Anything else to consider for v3?

Kevin

  reply	other threads:[~2011-03-09 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 12:30 [Qemu-devel] [PATCH v2] Add qcow2 documentation Kevin Wolf
2011-03-09 13:08 ` Stefan Hajnoczi
2011-03-09 13:55   ` Kevin Wolf [this message]
2011-03-09 14:28     ` Stefan Hajnoczi

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=4D7786E3.9070704@redhat.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.