That sounds reasonable. Thanks!

s/single kernel module/single loadable kernel module/ to differentiate
from modules in /boot/kernel/kernel.

Apply christos clarification.

Clean up document description and devfs_lookup.
The document description was broken on apropos due to macros,
and make devfs lowercase. The devfs_lookup was changed from
a non existent xref to a function.

Copy, thanks!

That's so exciting! Unfortunately, I have already failed at the very first step, I didn't fix the approved trailed in the commit log.

Revert attempt to sort contrib-comitters after realizing the doc said
sorted by last name. It is not sorted by last name.

Thanks! This is great info. I'll reflect on proper wording to reflect that it's designed to work on potentially unknown hardware.

Revert s/Dv/Sy/g, I did that to align with sysexits(3), however this was
a mistake as I think apropos Dv=EX_USAGE is an outstanding workflow. I
now believe that error messages should always be Dv.

Sorry, I forgot about moving filesystem manpages for freebsd 15!

Maybe helpful additional context:
Netbsd manpage says "Modifies the -l and -s options, causing the sizes to be reported in bytes displayed in a human readable format.".
Illumos manpage says "All sizes are scaled to a human readable format, for example, 14K, 234M, 2.7G, or 3.0T. Scaling is done by repetitively dividing by 1024. The last --si or -h option determines the divisor used."

Maybe "Show the file size in bytes with the following unit suffixes"?

bump date

Yes, style.mdoc(5) says "in case the longest item is too long and hurts readability, the reccomendattion is to set the -width argument to indent". I wasn't sure how to put that in the msg.

I don't know if this syntax is acceptable for referencing the src commit?

update to remove from release hw notes for 14.[0-2]

Thank you, I will fix them.

I don't see any leftover references to twe(4) using man -K "twe 4" "twe \(4" in the rest of the manual either.

Thank you for including me! When this passes I can remove it from the HW relnotes: https://reviews.freebsd.org/D48405.

I sure wish I could sneak the search word comment in here somewhere, but I was unable to figure out anything that seemed reasonable for the style of this doc.

Humble ping? I feel it's time for me to get started on 13.5 hw notes.

The manpage changes look great to me!

I'm so excited to test this driver this weekend! Thank you so much for submitting this! All of the suggestions I made are to bring it into alignment with the rest of the freebsd manual and are specified in the manual page style guide, style.mdoc(5). Sorry I'm so late.

I like total 131M with -h.

I do not like long options. We have a different culture and tradition that has a steep learning curve, but has led to the last living usable, daily driveable CLI. Long options are great for scripts but ruin the usability of CLI as a UX. This is just a comment and not a request for changes or nack. Cc'ing community leaders for review, and manpages since this is a manpage change.

Hi, is jrm's suggestion acceptable to everyone? I feel this would be really helpful without going too far.

Hi! This is a really interesting proposal! I always wished it did this, but also thought there was almost certainly some excellent reason why it hasn't. Since this is the foundation of userspace generations of scripts are built from, and thy Holy POLA of FreeBSD, I'm going to CC community leaders and grandmasters. Please forgive the disruption if this is undesirable. Thanks!

Super cool! Unfortunately I am not able to apply this to main with git-arc.sh patch -c D48368.

Sir, using current from yesterday i see a xref to this page in DEVICE_ATTACH(9), the diagnostics section of mlx(4) and twe(4), and the function appears to still be used in stand/kshim/bsd_kernel.*, sys/kern/subr_bus.c, and sys/sys/bus.h.

OG triple OG grandmaster jhb,
Please excuse my changing reviewers on your review.
People that subscribe to manpages are so excited to see draft manpages, and you're a a legend so i think it would excite at least most of them to see you have posted a draft manpage in their mboxen.

Here's what I've got so far for the manual. I ordered some parts to test but they're not all here yet.

Really, this syntax needs to be documented in src.conf(5) but I'm still studying makeman to figure out how to do that.

Also cc'ing bz

Fix acquire typo, thanks @pauamma!

Fix sentence typo, thanks @rpokala!

Manpage looks awesome. stderr(4) could also be used with Xr.

Wow! That was super cool. Thanks!

I'm not seeing it in the section 7 pdf here: https://www.bell-labs.com/usr/dmr/www/1stEdman.html

Just something to note I noticed today, style.mdoc(5) says not to use spaces in the synopsis pipes. This does conflict with the upstream mdoc style guides, and we more often seem to use spaces.

Merge 8188CE & 8188EE; bump date.

LGTM from a manpages standpoint (not a programmer).

Update commit message per instructions.

Should we mention re-enabling visibility of the hardware notes here?

Humble ping?

Thank you. How does it work since this is not doc? Since you have a src bit and have approved it, do I commit this? Also, in general, if you have approved it, do I still wait for Sergio? If not, do I put him as implicit or do I omit from the commit message?