From: Eric Biggers <ebiggers@google.com>
To: linux-xfs@vger.kernel.org
Cc: Eric Biggers <ebiggers@google.com>
Subject: [PATCH] xfs_io.8: remove duplicate .TP commands
Date: Mon, 28 Nov 2016 14:43:16 -0800 [thread overview]
Message-ID: <1480372996-41456-1-git-send-email-ebiggers@google.com> (raw)
The right margin of the xfs_io man page was being pushed inwards due to
extra .TP commands, making all the text below hard to read.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
man/man8/xfs_io.8 | 4 ----
1 file changed, 4 deletions(-)
diff --git a/man/man8/xfs_io.8 b/man/man8/xfs_io.8
index 885df7f..efdba13 100644
--- a/man/man8/xfs_io.8
+++ b/man/man8/xfs_io.8
@@ -486,7 +486,6 @@ to read (in bytes)
.RE
.PD
.TP
-.TP
.BI "seek \-a | \-d | \-h [ \-r ] [ \-s ] offset"
On platforms that support the
.BR lseek (2)
@@ -527,7 +526,6 @@ both data and holes are displayed together or performing a recusively display.
.RE
.PD
.TP
-.TP
.BI "reflink [ \-C ] [ \-q ] src_file [src_offset dst_offset length]"
On filesystems that support the
.B XFS_IOC_CLONE_RANGE
@@ -557,7 +555,6 @@ Do not print timing statistics at all.
.RE
.PD
.TP
-.TP
.BI "dedupe [ \-C ] [ \-q ] src_file src_offset dst_offset length"
On filesystems that support the
.B XFS_IOC_FILE_EXTENT_SAME
@@ -586,7 +583,6 @@ Do not print timing statistics at all.
.RE
.PD
.TP
-.TP
.BI "copy_range [ -s " src_offset " ] [ -d " dst_offset " ] [ -l " length " ] src_file"
On filesystems that support the
.BR copy_file_range (2)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-11-28 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 22:43 Eric Biggers [this message]
2016-11-29 20:10 ` [PATCH] xfs_io.8: remove duplicate .TP commands Christoph Hellwig
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=1480372996-41456-1-git-send-email-ebiggers@google.com \
--to=ebiggers@google.com \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).