Date: Tue, 21 May 2024 14:07:09 +0000 From: Marcin Cieslak <saper@saper.info> To: Warner Losh <imp@bsdimp.com> Cc: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= <des@freebsd.org>, current@freebsd.org Subject: Re: __memcpy_chk family of functions Message-ID: <18p47p63-5no5-p6r9-30rq-srpqpp196522@fncre.vasb> In-Reply-To: <CANCZdfrMYu5L4np%2B0kiAJCMOEugAgVeY0N5Tm%2B%2BOkFR8U9VY8Q@mail.gmail.com> References: <20qspnq2-8qp0-pq49-rq65-986n0q4r6rqq@fncre.vasb> <86msojvgfb.fsf@ltc.des.dev> <CANCZdfrMYu5L4np%2B0kiAJCMOEugAgVeY0N5Tm%2B%2BOkFR8U9VY8Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18p47p63-5no5-p6r9-30rq-srpqpp196522>