From: Bill Sommerfeld <sommerfeld@hamachi.org>
To: developer@lists.illumos.org
Subject: [REVIEW] 16703 types.h.3head has incorrect type for LP64 ino_t
Date: Fri, 16 Aug 2024 12:11:58 -0700 [thread overview]
Message-ID: <a94c1fd2-bb19-41d2-b52f-1eeb13a2eba2@hamachi.org> (raw)
Issue: https://www.illumos.org/issues/16703
CR: https://code.illumos.org/c/illumos-gate/+/3633
Diff:
https://code.illumos.org/~diff/bef1aec5885d287b4125c591ab88105ee4489155
This is a small correction to the types.h.3HEAD man page, correcting
the type of ino_t to match what the header actually defines; I also
added a cross-reference to lfcompile(7).
Thanks for your review.
- Bill
reply other threads:[~2024-08-16 19:12 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=a94c1fd2-bb19-41d2-b52f-1eeb13a2eba2@hamachi.org \
--to=sommerfeld@hamachi.org \
--cc=developer@lists.illumos.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).