[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Qemu-block] [PATCH] qemu-img: Document --force-share /
From: |
Kashyap Chamarthy |
Subject: |
Re: [Qemu-devel] [Qemu-block] [PATCH] qemu-img: Document --force-share / -U |
Date: |
Thu, 7 Dec 2017 11:58:27 +0100 |
User-agent: |
NeoMutt/20171027 |
On Thu, Dec 07, 2017 at 04:44:53PM +0800, Fam Zheng wrote:
> Signed-off-by: Fam Zheng <address@hidden>
> ---
> qemu-img.texi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/qemu-img.texi b/qemu-img.texi
> index fdcf120f36..3aa63aad55 100644
> --- a/qemu-img.texi
> +++ b/qemu-img.texi
> @@ -57,6 +57,14 @@ exclusive with the @var{-O} parameters. It is currently
> required to also use
> the @var{-n} parameter to skip image creation. This restriction may be
> relaxed
> in a future release.
>
> address@hidden --force-share (-U)
> +
> +If specified, qemu-img will open the image with shared permissions, which
> makes
Does 'texi' requires to quote tools like `qemu-img` (or single quotes),
to highlight them in documentation?
> +it less likely to conflict with a running guest's permissions due to image
> +locking. For example, this can be used to get the image information (with
> +'info' subcommand) when the image is used by a running guest. Note that this
> +could produce inconsistent result because of concurrent metadata changes,
> etc..
Super nit-pick: an ellipsis[*] is three dots :-), so, when applying you
might want to: s/../.../
[*] https://dictionary.cambridge.org/dictionary/english/ellipsis
Regardless:
Reviewed-by: Kashyap Chamarthy <address@hidden>
[...]
--
/kashyap