From: Fam Zheng <famz@redhat.com>
To: John Arbuckle <programmingkidx@gmail.com>
Cc: kwolf@redhat.com, mreitz@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img.c: Add examples section
Date: Fri, 3 Aug 2018 10:10:36 +0800 [thread overview]
Message-ID: <20180803021036.GB16395@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180803005015.5116-1-programmingkidx@gmail.com>
On Thu, 08/02 20:50, John Arbuckle wrote:
> Add an examples section to the help output.
>
> Signed-off-by: John Arbuckle <programmingkidx@gmail.com>
> ---
> qemu-img.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 1acddf693c..f77c82695d 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -199,6 +199,17 @@ static void QEMU_NORETURN help(void)
>
> printf("%s\nSupported formats:", help_msg);
> bdrv_iterate_format(format_print, NULL);
> +
> + printf("\n\nExamples:\n\n"
> + "Create: qemu-img create -f qcow2 image.qcow2 10G\n\n"
> + "Info: qemu-img info image.qcow2\n\n"
> + "Resize: qemu-img resize image.qcow2 20G\n\n"
> + "Convert: qemu-img convert -f raw -O qcow2 image.img image.qcow2\n\n"
> + "Check: qemu-img check image.qcow2\n\n"
> + "Map: qemu-img map -f qcow2 --output=human image.qcow2\n\n"
> + "Rebase: qemu-img rebase -b new_backing_file.qcow2 image.qcow2"
> + );
The text looks good but maybe it's better to condense the section by using only
one \n between command lines instead of two?
Fam
> +
> printf("\n\n" QEMU_HELP_BOTTOM "\n");
> exit(EXIT_SUCCESS);
> }
> --
> 2.14.3 (Apple Git-98)
>
>
next prev parent reply other threads:[~2018-08-03 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 0:50 [Qemu-devel] [PATCH] qemu-img.c: Add examples section John Arbuckle
2018-08-03 2:10 ` Fam Zheng [this message]
2018-08-03 2:34 ` Programmingkid
2018-08-03 8:46 ` Fam Zheng
2018-08-03 12:40 ` Programmingkid
2018-08-13 16:36 ` Max Reitz
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=20180803021036.GB16395@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-block@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).