[PATCH blktests 4/4] new: guide long command options

[Shin'ichiro Kawasaki]

In the past, command option confusion caused a script bug. The command
option definition change and command option misunderstanding were the
cause. To avoid such troubles, guide to use long command options.

Link: https://lore.kernel.org/linux-nvme/Zbu2qJGoz9UQfPw7@kbusch-mbp.dhcp.thefacebook.com/
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki at wdc.com>
---
 new | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/new b/new
index 4773175..58b5006 100755
--- a/new
+++ b/new
@@ -279,6 +279,9 @@ test() {
 # - Use the \$() form of command substitution instead of backticks.
 # - Use bash for loops instead of seq. E.g., for ((i = 0; i < 10; i++)), not
 #   for i in \$(seq 0 9).
+# - Use long command options instead of short options for readability and
+#   stability: e.g., 'nvme io-passthru --opcode X' is recommended over
+#   'nvme io-passthru -o X'.
 #
 # Please run \`make check\` after your test is done to check for shell
 # scripting errors and other mistakes.
-- 
2.55.0