Date: Mon, 28 Aug 2023 16:54:10 -0600 From: Warner Losh <imp@bsdimp.com> To: Mark Millard <marklmi@yahoo.com> Cc: "<dev-commits-src-main@freebsd.org>" <dev-commits-src-main@freebsd.org> Subject: Re: git: af93fea71038 - main - timerfd: Move implementation from linux compat to sys/kern Message-ID: <CANCZdfqhbzgt7X6vp5SrvvqkARrcxx87ywW5P7EQQWzx%2BV%2BJyA@mail.gmail.com> In-Reply-To: <8874149F-C8FF-4EDD-AECC-23E95D3A1C62@yahoo.com> References: <8874149F-C8FF-4EDD-AECC-23E95D3A1C62.ref@yahoo.com> <8874149F-C8FF-4EDD-AECC-23E95D3A1C62@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000417cdc0604039384 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Aug 28, 2023, 4:37 PM Mark Millard <marklmi@yahoo.com> wrote: > Warner Losh <imp_at_bsdimp.com> wrote on > Date: Mon, 28 Aug 2023 21:49:16 UTC : > > > On Mon, Aug 28, 2023 at 3:27=E2=80=AFPM Kyle Evans <kevans@freebsd.org>= wrote: > > > > > . . . > > > > > > > . . . > > > > And I totally acknowledge there were some issues with the import. I > > accept responsibility for not catching them. thankfully, Jake is workin= g > > to address them and we have enough time before 14.0. I'm also making > > notes for what to do differently next time. One is clearly to loop Alex= ey > > into the process: I didn't think about it before the commit, but in > > hindsight > > it's really something I should have done. > > > > > I'll note that https://www.freebsd.org/releases/14.0R/schedule/ > makes no distinction for KBI breakage types of changes vs. KBI > changes in general for its listed KBI restriction: > > QUOTE > Code slush begins / KBI freeze 4 August 2023 3 August 2023 > . . . Additionally, there can be no changes to the KBI > until main is branched to stable/14. > END QUOTE > > I'd not know if the wording is stronger than the intent. It is > difficult to word things for a complicated intent. But, for > all I know, the wording could match the intent. > Several other additions happened in that time frame. I've always read it as "to established" before KBIs. But this is really more an ABI addition to userland. No K involved. Warner =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --000000000000417cdc0604039384 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" = class=3D"gmail_attr">On Mon, Aug 28, 2023, 4:37 PM Mark Millard <<a href= =3D"mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>> wrote:<br></div><bl= ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #= ccc solid;padding-left:1ex">Warner Losh <<a href=3D"http://imp_at_bsdimp= .com" rel=3D"noreferrer noreferrer" target=3D"_blank">imp_at_bsdimp.com</a>= > wrote on<br> Date: Mon, 28 Aug 2023 21:49:16 UTC :<br> <br> > On Mon, Aug 28, 2023 at 3:27=E2=80=AFPM Kyle Evans <<a href=3D"mail= to:kevans@freebsd.org" target=3D"_blank" rel=3D"noreferrer">kevans@freebsd.= org</a>> wrote:<br> > <br> > > . . .<br> > ><br> > <br> > . . .<br> > <br> > And I totally acknowledge there were some issues with the import. I<br= > > accept responsibility for not catching them. thankfully, Jake is worki= ng<br> > to address them and we have enough time before 14.0. I'm also maki= ng<br> > notes for what to do differently next time. One is clearly to loop Ale= xey<br> > into the process: I didn't think about it before the commit, but i= n<br> > hindsight<br> > it's really something I should have done.<br> > <br> <br> <br> I'll note that <a href=3D"https://www.freebsd.org/releases/14.0R/schedu= le/" rel=3D"noreferrer noreferrer" target=3D"_blank">https://www.freebsd.or= g/releases/14.0R/schedule/</a><br> makes no distinction for KBI breakage types of changes vs. KBI<br> changes in general for its listed KBI restriction:<br> <br> QUOTE<br> Code slush begins / KBI freeze 4 August 2023 3 August 2023<br> . . . Additionally, there can be no changes to the KBI<br> until main is branched to stable/14.<br> END QUOTE<br> <br> I'd not know if the wording is stronger than the intent. It is<br> difficult to word things for a complicated intent. But, for<br> all I know, the wording could match the intent.<br></blockquote></div></div= ><div dir=3D"auto"><br></div><div dir=3D"auto">Several other additions happ= ened in that time frame. I've always read it as "to established&qu= ot; before KBIs.</div><div dir=3D"auto"><br></div><div dir=3D"auto">But thi= s is really more an ABI addition to userland.=C2=A0 No K involved.</div><di= v dir=3D"auto"><br></div><div dir=3D"auto">Warner</div><div dir=3D"auto"><b= r></div><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"g= mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l= eft:1ex"> =3D=3D=3D<br> Mark Millard<br> marklmi at <a href=3D"http://yahoo.com" rel=3D"noreferrer noreferrer" targe= t=3D"_blank">yahoo.com</a><br> <br> </blockquote></div></div></div> --000000000000417cdc0604039384--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqhbzgt7X6vp5SrvvqkARrcxx87ywW5P7EQQWzx%2BV%2BJyA>