From: Theodore Ts'o <tytso@mit.edu>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/6] kvm-xfstests: update command line help
Date: Fri, 19 Aug 2016 09:42:38 -0400 [thread overview]
Message-ID: <20160819134238.GG10888@thunk.org> (raw)
In-Reply-To: <1471553651-9547-4-git-send-email-dmonakhov@openvz.org>
On Fri, Aug 19, 2016 at 12:54:08AM +0400, Dmitry Monakhov wrote:
> diff --git a/kvm-xfstests/util/parse_cli b/kvm-xfstests/util/parse_cli
> index 83400ea..edbbafa 100644
> --- a/kvm-xfstests/util/parse_cli
> +++ b/kvm-xfstests/util/parse_cli
> @@ -26,10 +26,47 @@ print_help ()
> echo " -o opts - Extra kernel command line options"
> echo " -r ram - Specify memory to be used in megabytes"
> echo " -X test - Exclude test from running"
> + echo " --no-punch - Do not run tests w/ patch hole"
> + echo " --no-collapse - Do not run tests w/ collapse range"
> + echo " --no-insert - Do not run tests w/ insert range"
> + echo " --no-zero - Do not run tests w/ zero range"
The reason why I don't document these options is they depend on an
out-of-tree patch for xfstests. It's in my githup repo, but it's not
something which xfstests upstream has seen fit to take.
> if test "$GCE_XFSTESTS" != "yes" ; then
> echo " --kernel file - Boot the specified kernel"
>
> + else
> + echo "GCE speciffic commands:"
> + echo " ls-instances"
> + echo " ls|ls-instances"
> + echo " rm|rm-instances|abort|abort-instances"
> + echo " start|start-instance|start-instances"
> + echo " stop|stop-instance|stop-instances"
> + echo " ls-disks|ls-disk"
> + echo " rm-disks|rm-disk"
> + echo " ls-results|ls-gcs"
> + echo " rm-results|rm-gcs"
> + echo " get-results"
> + echo " setup"
> + echo " ssh"
> + echo " console"
> + echo " serial"
> + echo " get-results"
> + echo " create-image"
> + echo " export-image"
> + echo " import-image"
> + echo " --numa"
> + echo " --log"
> + echo " --local-ssd"
> + echo " --pmem-device"
> + echo " --machtype"
> + echo " --image-project"
> + echo " --instance-name"
> + echo " --no-virtio-rng"
> fi
> + echo "Base image update commands:"
> + echo " --update-xfstests-tar"
> + echo " --update-xfstests"
> + echo " --update-files"
> + echo
> echo " --no-log - Don't save the log file for this run"
> echo " --no-action - Print the command to start the VM"
> echo ""
The options don't belong next to the GCE specific commands. And
gce-import, as well as the base image update options, are really
intended for the maintainer (e.g., for me to update the xfstests-cloud
public image project).
The main issue is I'm a bit concerned about making the help message
too long. My long term vision is to go in the direction of git and
gcloud's style of help messages / man pages. So gce-xfstests --help
and kvm-xfstests --help will display a list of the most commonly used
/ useful commands and options. And where "gce-xfstests get-results
--help" will display a full man page for the get-results subcommand,
and "gce-xfstests help commands" will display a full list of all
commands, and "gce-xfstests help topics" will allow you to see the
documentation currently available as markdown files in Documentation.
Cheers,
- Ted
next prev parent reply other threads:[~2016-08-19 13:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 20:54 [PATCH 0/6] xfstests-bld: Fixes and improvements v1 Dmitry Monakhov
[not found] ` <1471553651-9547-7-git-send-email-dmonakhov@openvz.org>
2016-08-19 5:21 ` [PATCH 6/6] Add dockerfile Theodore Ts'o
2016-08-19 9:27 ` Dmitry Monakhov
2016-08-19 23:29 ` Theodore Ts'o
2016-08-20 11:31 ` Dmitry Monakhov
2016-08-20 19:45 ` Theodore Ts'o
2016-08-21 2:55 ` Theodore Ts'o
2016-08-21 12:02 ` Dmitry Monakhov
2016-08-21 14:26 ` Theodore Ts'o
2016-08-21 15:35 ` Theodore Ts'o
2016-08-22 8:07 ` Dmitry Monakhov
[not found] ` <1471553651-9547-5-git-send-email-dmonakhov@openvz.org>
2016-08-19 13:32 ` [PATCH 4/6] xfstest-bld: use parallel gzip if possible Theodore Ts'o
2016-08-20 22:52 ` Theodore Ts'o
[not found] ` <1471553651-9547-2-git-send-email-dmonakhov@openvz.org>
2016-08-19 13:35 ` [PATCH 1/6] xfstests-bld: build update xfstests repo Theodore Ts'o
[not found] ` <1471553651-9547-3-git-send-email-dmonakhov@openvz.org>
2016-08-19 13:35 ` [PATCH 2/6] fix build typos Theodore Ts'o
[not found] ` <1471553651-9547-4-git-send-email-dmonakhov@openvz.org>
2016-08-19 13:42 ` Theodore Ts'o [this message]
2016-08-19 13:51 ` [PATCH 3/6] kvm-xfstests: update command line help Dmitry Monakhov
2016-08-20 22:19 ` Theodore Ts'o
[not found] ` <1471553651-9547-6-git-send-email-dmonakhov@openvz.org>
2016-08-19 13:44 ` [PATCH 5/6] kvm-xfstests: add initrd support Theodore Ts'o
2016-08-19 13:59 ` Dmitry Monakhov
2016-08-19 23:40 ` Theodore Ts'o
2016-08-20 22:35 ` Theodore Ts'o
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=20160819134238.GG10888@thunk.org \
--to=tytso@mit.edu \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.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.