Date: Sun, 23 Feb 2020 15:34:13 -0500 From: Ed Maste <emaste@freebsd.org> To: freebsd-stable stable <freebsd-stable@freebsd.org> Subject: Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life Message-ID: <CAPyFy2CiER92or_zgdVuT=9Tfj3=7Dvht01ePg0FjMpWkLnx1Q@mail.gmail.com> In-Reply-To: <DM6PR02MB5228FB1266ABEB56C10A5364FAEF0@DM6PR02MB5228.namprd02.prod.outlook.com> References: <20200217231452.717FA1E820@freefall.freebsd.org> <CAFYkXjmZi1-MB6W0HsMx9gHek7Xg5heoSKKWkNTnw74dxRTwAw@mail.gmail.com> <DM6PR02MB5228FB1266ABEB56C10A5364FAEF0@DM6PR02MB5228.namprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Feb 2020 at 12:48, Gerard E. Seibert <gerard_seibert@outlook.com> wrote: > > Until they squash that bug, they should not be in a rush to push out > the door another defective model. Unfortunately complaining that there's a bug in 12.0 or 12.1 or providing additional reports of this will do nothing to help resolve the issue. I can suggest two ways folks can help get this resolved: build and test kernels (with guidance from interested developers) to bisect and identify the offending commit/test potential patches, or make a system available to willing developer(s).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2CiER92or_zgdVuT=9Tfj3=7Dvht01ePg0FjMpWkLnx1Q>