User Details
- User Since
- Apr 2 2019, 6:04 PM (357 w, 1 d)
Sun, Feb 1
Fri, Jan 30
Approved once the listed issues are fixed, thanks!
Approved once the minor issues listed are fixed, thanks!
Tue, Jan 27
Sun, Jan 25
Sun, Jan 18
Sat, Jan 17
Approved, thanks!
Approved, thanks!
Wed, Jan 14
A few minor changes and it is ready to merge.
Thanks for your report!
Sat, Jan 10
A few changes and it is ready to merge. Thanks for your report!
Approved, thanks!
Fri, Jan 9
Tue, Jan 6
Jan 2 2026
Dec 30 2025
A few small fixes and it is ready to merge.
Thanks!
Dec 28 2025
Since I have been put in the reviewers, let me add my two cents.
A few small fixes and it is ready to merge.
Thanks for you report!
Dec 26 2025
Dec 23 2025
A few small changes and it is ready for merge. The report also needs to have one sentence per line (I can do it at merge time if you prefer).
Thanks!
A few small changes and it is ready for merge. The report also needs to have one sentence per line (I can do it at merge time if you prefer).
Thanks!
Approved, thanks!
Approved, thanks!
Dec 21 2025
Calls for status reports sent to developers@ in BCC on the 15th of December have arrived successfully.
So this change is not necessary anymore and I abandon the revision.
Dec 14 2025
Nov 30 2025
I have added bapt and pi to the reviewers as postmaster members because the issue probably started with some recent change in developers mailing list configuration. Now they are aware and can have a word about it if they want. But I do not think that the configuration should be changed: I believe stop sending status reports to developers@ is the right solution.
Revision's link and revision's author referenced in the mailing list: https://lists.freebsd.org/archives/dev-commits-doc-all/2025-November/004816.html
Merged with changes as https://cgit.freebsd.org/doc/commit/?id=ecd8cc0702da9d3fff4c8b18d2c9236d48cdea83 (forgot to put it in the commit message, sorry)