diff options
| author | Christer Ekholm <[email protected]> | 2016-05-23 19:20:42 +0200 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2016-05-23 10:20:42 -0700 |
| commit | 3491d6eb06c3e2e6f337bd57b6137ccff4b8c077 (patch) | |
| tree | b65cd0abf60061690e08f6969f8041c3c3735a53 /cmd/zdb | |
| parent | 9baaa7deae45c8556dfd79b2011234da5cb37b3a (diff) | |
Consistently use parsable instead of parseable
This is a purely cosmetical change, to consistently prefer one of
two (both acceptable) choises for the word parsable in documentation and
code. I don't really care which to use, but acording to wiktionary
https://en.wiktionary.org/wiki/parsable#English parsable is preferred.
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #4682
Diffstat (limited to 'cmd/zdb')
| -rw-r--r-- | cmd/zdb/zdb.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cmd/zdb/zdb.c b/cmd/zdb/zdb.c index cbc98d24c..3311a6e6f 100644 --- a/cmd/zdb/zdb.c +++ b/cmd/zdb/zdb.c @@ -172,7 +172,7 @@ usage(void) "-e to specify path to vdev dir\n"); (void) fprintf(stderr, " -x <dumpdir> -- " "dump all read blocks into specified directory\n"); - (void) fprintf(stderr, " -P print numbers in parseable form\n"); + (void) fprintf(stderr, " -P print numbers in parsable form\n"); (void) fprintf(stderr, " -t <txg> -- highest txg to use when " "searching for uberblocks\n"); (void) fprintf(stderr, " -I <number of inflight I/Os> -- " |