Date: Mon, 3 Aug 2020 13:13:31 -0600 From: Alan Somers <asomers@freebsd.org> To: FreeBSD <freebsd-stable@freebsd.org> Subject: Re: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 Message-ID: <CAOtMX2jX29T4f5z2HasZSgcLMWjom8Hc_-yXXiCp8iZJnuLCqA@mail.gmail.com> In-Reply-To: <DM6PR02MB5228312BC4C0326F816A36A5FA4D0@DM6PR02MB5228.namprd02.prod.outlook.com> References: <DM6PR02MB5228312BC4C0326F816A36A5FA4D0@DM6PR02MB5228.namprd02.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Pro tip: if you want people to read the message, put the bug's title in the subject line. This is a high volume mailing list, and most people won't follow a link without good motivation. -Alan On Mon, Aug 3, 2020 at 1:04 PM Gerard E. Seibert <gerard_seibert@outlook.com> wrote: > I am just inquiring to see if any progress had been made regarding > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666>. > > FreeBSD 12.2 is due out in October and version 13.0 only five months > later. At present, this bug infects both the 12.x and 13.x branches > making updating systems beyond 11.x impossible for users of the > afflicted systems. The fact that this bug has gone unremedied for so > long is somewhat disheartening. > > Thanks! > > -- > Gerard >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2jX29T4f5z2HasZSgcLMWjom8Hc_-yXXiCp8iZJnuLCqA>