Found another minor grammatical nit. I don't really understand enough to know why we would choose "a" or "the" for these. Also, would you please "Relnotes: yes" this?
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 28 2026
In D48872#1327993, @bcr wrote:Is there more work on this to come @felix.the.red_gmail.com ? We would really like to see this man page in FreeBSD.
If you're to busy, we can probably finish the rest ourselves. Just wanting to make sure this is still actively being worked on. Thanks!
Thank you so much for doing this!
Jun 27 2026
I think we can put this in a new .toml and use for local env
In D57761#1327566, @carlavilla wrote:Hello,
I've been looking into this.
I think the simplest solution would be:In the Makefile, inside the run-local target, add another configuration file, like "hugo.dev.toml" or "hugo.local.toml"
And inside this new file put this:ignoreFiles = [
"\\.po$", "/releases/([1-9]|1[0-2])\\.", "/releases/13\\.[0-4]",]
What do you think?
Hi! Can we have a little skeleton manpage in this commit? Here is an example of a minimum implementation that is enormously useful, just 40 lines: https://freshbsd.org/freebsd/src/commit/fd1ee28bd01429aa8c38199d5fc069e8b0b75442
Jun 26 2026
But your comment is fair that the entire section should be re-headed CAVEATS. Do you want me to pull in the existing outliers into CAVEATS too ?
No problem, I'm happy to help.
Looks good from manpages! I defer to senior colleagues for the rest of the implementation.
Hi! Thank you so much for working on this!
Jun 25 2026
I was so excited to see this in my inbox. People have been asking me to write this for years and I tell them I wish that I could. Thank you so much for doing this.
Jun 24 2026
Well, they still need to update their loader and this section is still applicable.
Could we also put some sbom tags?
Thanks @emaste !
Perhaps I have never explained it well enough, but technical writing is like code optimization. You have to be careful to build what you actually need, and not the stuff around it. Premature optimization goes right off the rails and actually can ruin performance. Similarly, extra ideas spend the reader's clever bits and they can easily get overwhelmed. Senior colleagues like you know effectively everything, but we need give them only the answer that the doc is after. Every word has a concept backing it, and what makes the doc not-abrasive is that it sufficiently explains exactly what they're looking for, and they don't need to rest after reading it. Maybe I'm still not explaining it well enough, sorry for that.
Of course this doc is about FreeBSD, but I don't think this is excessive. It is useful to clarify that we are talking about FreeBSD's boot methods, not implying that a given CPU arch in general uses a given method.
Jun 23 2026
found a few extra nits
Updating this in two identical files is bad. Asciidoctor has native redirects, I have proposed using these here, mostly just to brief our team that it's this easy: https://reviews.freebsd.org/D57792
Updating this in two identical files is bad. Asciidoctor has native redirects, I have proposed using these here, mostly just to brief our team that it's this easy: https://reviews.freebsd.org/D57792
After discussing this with @cperciva, I would like to pursue an alternate course of action where instead of using mounts, i use segments, then we use a build knob like -WITH-UNSUPPORTED-RELNOTES if we want that.
In D57761#1324263, @roberto wrote:As said in IRC: adding all these files (which will never change, except if we change the stylesheet/theme) will duplicate these when using hugo build in public before the deployment.
LGTM but please remove "FreeBSD", this document is obviously about FreeBSD and when I have had my friends unrelated to FreeBSD review my drafts, they have told me that the constant reiteration makes it more tedious. Related: https://reviews.freebsd.org/D57606
This is cool! Please add the docs to bhyvectl as well!
i turned this one back over to dch@ and he landed it
- i have no idea if this is a reasonable solution
- it will be possible because all the source is still where it was originally, just building it is not done by default.
fixing some of the tags didn't work, trim to only the fixes that are working cleanly
Jun 22 2026
the idx size typo was my own, sorry! add back the check.
In D57481#1323718, @dch wrote:committed in dd2e9aa21a45
Jun 21 2026
Can we fix https://www.freebsd.org/status/feed.xml instead of adding a new one?
nevermind on 50, seems like we do not want that.
- 20 is too short. Can we have 50?
- why does this combine security and errata if we have two separate feeds for that?
- can we please put the actual content in these?
Ping, the release has shipped so any changes to these instructions should be made ASAP.
I will since as the reviewer I was supposed to prevent these typos. Thanks guys!
Fix syntax escaping; thanks @0mp!
Jun 20 2026
Manpages looks good to me, thank you!
Add back kld_list. We need this to demonstrate the module name. Pointed out by @kevans. This should address imp's concerns.
