From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 216275] Incorrect fts_pathlen in fts(3) man page
Date: Sat, 23 Jul 2022 13:02:06 +0000 [thread overview]
Message-ID: <bug-216275-11311-to7h63aRUm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216275-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216275
--- Comment #1 from Philip Jones (philj56@gmail.com) ---
Another minor discrepancy I forgot to mention: the man page documents both
fts_pathlen and fts_namelen as having type short, but the glibc source assigns
type unsigned short to each.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-07-23 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 12:56 [Bug 216275] New: Incorrect fts_pathlen in fts(3) man page bugzilla-daemon
2022-07-23 13:02 ` bugzilla-daemon [this message]
2022-07-24 10:41 ` [Bug 216275] " bugzilla-daemon
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=bug-216275-11311-to7h63aRUm@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@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