Is it possible to fix the warning? If not that's fine.

Hate to say it, but make distclean && make checksum succeeded for me as-is.

Oh yeah, this is the one. 100% 👍 from me.

I'm a little confused by the logic.

(Is commenting on a closed review the Right Thing[tm] to do? Or should I be creating a separate one so as not to confuse things?)

In D55443#1272019, @ziaee wrote:

use database or compiler versions, i like that.
i like the text we've come up with so far otherwise.

@arrowd Thanks for making this happen!

I spent a looooong time with ChatGPT working on phrasing. Why is this one so tough?!

Updating patch with some markup that I'm seeing elsewhere in the file. In particular, this adds [.filename] tags.

@fuz when you have a chance, can you take a peek at this? Does this look correct?

Improving grammar to distract from being fuzzy on the markup.

In D55491#1271519, @gperciva_tarsnap.com wrote:

Sorry, did you actually change the dates? It looks like the version on Phabricator still lists 6/31 and 9/31. Is the website slow to update the diff it displays?

I'm not familiar with the calendar syntax, but calendar.freebsd has format date desc whereas calendar.status_reports has date: desc. Just making sure that that's intentional and acceptable. Other than that, these dates and descriptions all look correct to me.

I like this, but version … version reads a little oddly.

I think this looks great! I have no notes for you :-)

You're totally right. I grepped the doc repo just to be sure, and we don't have anything about using ${DEFAULT_VERSIONS}. If we had something (maybe in the handbook, as it's designed for end-users) we could reference it here instead maybe.

Looks great! And your wording on work/ is much better than mine was. Others you can consider:

I'm a big yes to this plan

In D54657#1262977, @dave_freedave.net wrote:

Thanks Adam! I think its ready for commit now.

This looks great, Dave! Are you ready for me to commit it?

In D54657#1262354, @dave_freedave.net wrote:

Actually I just hit the same test failure pkg-fallout had emailed me about. bee has a test here that I don't believe is correct.

sleep(3) does not promise to return within 1 seconds (or indeed any amount) of time after your requested sleep amount has elapsed. I'm sure it usually is going to be within 1 second, but I think this is a bad test.

In D54657#1253184, @dave_freedave.net wrote:

Here is what you are going to need if you want lua-language-server to pick up symbols when editing your neovim config:
[...]

So, here's the deal. This patch looks great, it tests perfectly for me, and I'm happy to commit it. Just give me a sign when you're ready and I'll make it happen.

So, here's the deal. This patch looks great, it tests perfectly for me, and I'm happy to commit it. Just give me a sign when you're ready and I'll make it happen.

Updated a comment to be correcter.

Thank you for all your patience. 2026 has been.... difficult.