From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:57912)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1TOVcr-0001is-01
	for qemu-devel@nongnu.org; Wed, 17 Oct 2012 11:33:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1TOVcl-0002lJ-Jn
	for qemu-devel@nongnu.org; Wed, 17 Oct 2012 11:33:40 -0400
Received: from mx1.redhat.com ([209.132.183.28]:22067)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1TOVcl-0002l4-CG
	for qemu-devel@nongnu.org; Wed, 17 Oct 2012 11:33:35 -0400
Message-ID: <507ECFCB.7000904@redhat.com>
Date: Wed, 17 Oct 2012 17:33:31 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
References: <1350192655-19706-1-git-send-email-kashyap.cv@gmail.com>
In-Reply-To: <1350192655-19706-1-git-send-email-kashyap.cv@gmail.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] qemu-img: document 'info --backing-chain
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Cc: qemu-devel@nongnu.org

Am 14.10.2012 07:30, schrieb Kashyap Chamarthy:
> From a6233277e17338f571dda27cd9192d764f824b18 Mon Sep 17 00:00:00 2001
> From: Kashyap Chamarthy <kashyap.cv@gmail.com>
> Date: Sun, 14 Oct 2012 09:51:18 +0530
> Subject: [PATCH v2] qemu-img: document 'info --backing-chain'
> 
> Signed-off-by: Kashyap Chamarthy <kashyap.cv@gmail.com>

> @@ -137,6 +141,19 @@ from the displayed size. If VM snapshots are stored in the disk image,
>  they are displayed too. The command can output in the format @var{ofmt}
>  which is either @code{human} or @code{json}.
>  
> +If a disk image has a backing file chain, information about each disk image in
> +the chain can be recursively enumerated by using the option @code{--backing-chain}.
> +
> +For instance, if you have an image chain like: 
> +
> +    base.qcow2 <- snap1.qcow2 <- snap2.qcow2 
> +
> +To enumerate information about each disk image in the above chain, starting from top to base, do:
> +    
> +    @example
> +    qemu-img info --backing-chain snap2.qcow2
> +    @end example
> +
>  @item snapshot [-l | -a @var{snapshot} | -c @var{snapshot} | -d @var{snapshot} ] @var{filename}
>  
>  List, apply, create or delete snapshots in image @var{filename}.

For me, this is rendered as:

           For instance, if you have an image chain like:

               base.qcow2 E<lt>- snap1.qcow2 E<lt>- snap2.qcow2

           To enumerate information about each disk image in the above
chain, starting from top to base, do:

               @example
               qemu-img info --backing-chain snap2.qcow2
               @end example

That is,  the arrows aren't quite right and @example is included
literally. Please fix and resubmit.

Kevin