Date: Fri, 8 Apr 2022 04:01:00 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-questions@freebsd.org Subject: Re: nvidia-driver and no update in /usr/ports/UPDATING Message-ID: <20220408040100.7ce89e7d46a0cea249a89711@sohara.org> In-Reply-To: <Yk%2Bfip5KdWYjn99h@cloud9.zyxst.net> References: <Yk9tEmvtQB5JEWoz@cloud9.zyxst.net> <Yk%2Bfip5KdWYjn99h@cloud9.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 8 Apr 2022 03:35:54 +0100 tech-lists <tech-lists@zyxst.net> wrote: > It's not just this. > > Look at this: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249252 Something might have happened if you're bug report had been more along the lines of ******************************************************* "UPDATING entry needed for ... change" ... change went in without an UPDATING entry which could surprise users and cause <insert consequences of missing the update>, an entry like ------- Burble wibble ... and do ... ------- would help prevent surprises and alert users to required changes. ******************************************************* With a CC to the port maintainer. That might get the job done, and help the project by backstopping developers who are too busy to dot the is and cross the ts every time instead of whining at them. It takes a little more effort and thought than firing off a ranting bug report like the one you refer to but it makes it easy for the person giving their free time to reading bug reports and deciding what to do. In this case they can leave it to the port maintainer - who can cut and paste your comment, edit it and commit. Otherwise they have to decide (on no evidence) that you're right about it being needed, look up the port maintainer and contact them about it who then has to compose an entry about an update they committed some time ago. Or they go on to the next bug report about a P0 security issue complete with the fix and forget about yours. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220408040100.7ce89e7d46a0cea249a89711>