<https://www.phoronix.com/news/FreeBSD-13.1-RC6-Released> refers to: <https://lists.freebsd.org/archives/freebsd-stable/2022-May/000762.html> The oldest Wayback Machine capture, <https://web.archive.org/web/20220506012657/https://lists.freebsd.org/archives/freebsd-stable/2022-May/000762.html>, was entitled: > FreeBSD 13.1-RC6 Now Available FreeBSD's list archive currently presents a different email: > nfs client's OpenOwner count increases without bounds
As far as I can tell, the required email currently has a different ID (000770, previously 000762): <https://lists.freebsd.org/archives/freebsd-stable/2022-May/000770.html> It seems that breakage occurred last year, some time between: * 2022-05-25, the proper content captured at <https://web.archive.org/web/20220525063710/https://lists.freebsd.org/archives/freebsd-stable/2022-May/000762.html> * 2022-06-12, the wrong content captured at <https://web.archive.org/web/20220612150139/https://lists.freebsd.org/archives/freebsd-stable/2022-May/000762.html>.
Another example … Bug 260994 refers to <https://lists.freebsd.org/archives/freebsd-hackers/2022-January/000741.html> (000741), which is currently: > Re: strange compiling problems on AMD Ryzen 5 5600G with freebsd-current – that is unrelated to the bug. At the time of me linking, it was probably this, from Warner: > Re: 5.9 points Re: 7.0 points 5.1 points Re: Call for Foundation-supported Project Ideas – that is currently <https://lists.freebsd.org/archives/freebsd-hackers/2022-January/000745.html> (000745).
(In reply to Graham Perrin from comment #2) Two more examples from the same period (January 2022). A) <https://web.archive.org/web/20220110221940/https://lists.freebsd.org/archives/freebsd-hackers/2022-January/000751.html> (000751) was: > Debugging a (potentially?) ZFS-related panic, and discussion about large patchsets <https://lists.freebsd.org/archives/freebsd-hackers/2022-January/000751.html> is now: > Re: Out-of-swap killer and SIGTERM signal B) <https://web.archive.org/web/20220128020223/https://lists.freebsd.org/archives/freebsd-hackers/2022-January/000800.html> (000800) was: > Re: Dragonfly Mail Agent (dma) in the base system <https://lists.freebsd.org/archives/freebsd-hackers/2022-January/000800.html> is now: > Re: Which disk is which?
We don't need the mailing lists themselves as CCs; they have way too many subscribers between them, particularly for something that only postmaster@ can do much about.
If I remember right, there was a time when some messages turned up missing or showing up in the wrong month/place --and the fixes involved renumbering to make room for those messages in the right places. This means that there was a time frame in which references were established that end up no longer referencing what was intended. Basically, once messed up, no adjustment would keep everything working as intended and a choice was made. If that is a correct memory, it may be that some of this is "already fixed as best we can".