Re: __memcpy_chk family of functions
- Reply: Dag-Erling_Smørgrav : "Re: __memcpy_chk family of functions"
- In reply to: Warner Losh : "Re: __memcpy_chk family of functions"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 21 May 2024 14:07:09 UTC
On Tue, May 21, 2024 at 12:16 AM Dag-Erling Smørgrav <des@freebsd.org> wrote: > The purpose of UPDATING is to document changes that break backward > compatibility, i.e. running old binaries on a newer world. > happened here is that you tried to run newer binaries on an older world, On Tue, 21 May 2024, Warner Losh wrote: > Also, our forward compatibility guarantees are extremely weak. Just for clarification: I am not complaining about my breakage. It was my stunt and it didn't work out, I got punished by sitting there and waiting for llvm to compile. I think this (useful) change should go into the future release notes as a new feature. Where and how should this be documented? Shall FreeBSD_version be bumped for this one? For example, when libsys got introduced, we could learn about this from the UPDATING file. I do not want UPDATING to be come unreadable or a copy of git log, though. Marcin