From: Eric Sandeen <sandeen@redhat.com>
To: fstests <fstests@vger.kernel.org>
Subject: [PATCH] xfs/293: tighten up checks for documented xfs_io commands
Date: Fri, 4 Dec 2015 15:18:14 -0600 [thread overview]
Message-ID: <56620316.4090104@redhat.com> (raw)
Some commands (like "zero") are simple words which commonly
occur in the manpage text even if they aren't documented as
commands.
Grep for " $COMMAND" instead of the bare word, because
the documented commands show up as indented.
This reveals that the "zero" command is not documented yet.
(It catches "help" too, because it's documented differently;
I'll fix that up in the manpage when I add "zero").
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/tests/xfs/293 b/tests/xfs/293
index d1a2853..ade6015 100755
--- a/tests/xfs/293
+++ b/tests/xfs/293
@@ -49,7 +49,7 @@ _supported_os IRIX Linux
echo "Silence is golden"
for COMMAND in `$XFS_IO_PROG -c help | awk '{print $1}' | grep -v "^Use"`; do
- man xfs_io | col -b | grep -wq $COMMAND || \
+ man xfs_io | col -b | grep -wq " $COMMAND" || \
echo "$COMMAND not documented in the xfs_io manpage"
done
next reply other threads:[~2015-12-04 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 21:18 Eric Sandeen [this message]
2015-12-11 9:25 ` [PATCH] xfs/293: tighten up checks for documented xfs_io commands Eryu Guan
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=56620316.4090104@redhat.com \
--to=sandeen@redhat.com \
--cc=fstests@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox