All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Kashyap Chamarthy <kashyap.cv@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-img: document 'info --backing-chain
Date: Wed, 17 Oct 2012 17:33:31 +0200	[thread overview]
Message-ID: <507ECFCB.7000904@redhat.com> (raw)
In-Reply-To: <1350192655-19706-1-git-send-email-kashyap.cv@gmail.com>

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

      parent reply	other threads:[~2012-10-17 15:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-14  5:30 [Qemu-devel] qemu-img: document 'info --backing-chain Kashyap Chamarthy
2012-10-14  6:21 ` [Qemu-devel] [PATCH]Re: " Kashyap Chamarthy
2012-10-15  9:01 ` [Qemu-devel] " Stefan Hajnoczi
2012-10-15 21:07 ` Eric Blake
2012-10-16  3:10   ` Kashyap Chamarthy
2012-10-17 15:33 ` Kevin Wolf [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=507ECFCB.7000904@redhat.com \
    --to=kwolf@redhat.com \
    --cc=kashyap.cv@gmail.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 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.