From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=41541 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PxJph-0008Ac-Q9 for qemu-devel@nongnu.org; Wed, 09 Mar 2011 08:53:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PxJpg-0001oU-LB for qemu-devel@nongnu.org; Wed, 09 Mar 2011 08:53:45 -0500 Received: from mx1.redhat.com ([209.132.183.28]:25405) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PxJpg-0001oL-B1 for qemu-devel@nongnu.org; Wed, 09 Mar 2011 08:53:44 -0500 Message-ID: <4D7786E3.9070704@redhat.com> Date: Wed, 09 Mar 2011 14:55:47 +0100 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH v2] Add qcow2 documentation References: <1299673824-11307-1-git-send-email-kwolf@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: qemu-devel@nongnu.org Am 09.03.2011 14:08, schrieb Stefan Hajnoczi: > On Wed, Mar 9, 2011 at 12:30 PM, Kevin Wolf 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 >> --- >> 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