From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: llseek.2, lseek.2, lseek64.3: Duplicate documentation?
Date: Mon, 5 Oct 2020 23:56:52 +0200 [thread overview]
Message-ID: <8b189f6d-1320-8ea5-2539-e0c1fc45e75a@gmail.com> (raw)
Hi Michael,
lseek64.3 documents lseek64(), and it also documents lseek(), lseek64(),
and _llseek().
Then there's lseek.2 which documents lseek(),
and llseek.2, which awkwardly only documents _llseek() only.
And then _llseek.2 which is a link to llseek.2.
Maybe you would like to reorganize those pages.
Cheers,
Alex
reply other threads:[~2020-10-05 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8b189f6d-1320-8ea5-2539-e0c1fc45e75a@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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).