Date: Tue, 11 Feb 2025 01:11:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 206360] gstat should sort by device name Message-ID: <bug-206360-227-09MSdjFFdn@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206360-227@https.bugs.freebsd.org/bugzilla/> References: <bug-206360-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206360 --- Comment #5 from Terry Kennedy <terry-freebsd@glaver.org> --- (In reply to Mark Linimon from comment #4) The snark version: I don't think anyone could be less motivated. The polite version: I agree that there are lots of bugs that should be tria= ged and assigned that aren't getting handled due to a lack of resources. A "Waiting" or some similar state name in Bugzilla to indicated that a bug re= port has been reviewed, but there are no resources to address it might also be useful, particularly for "affects only me" bugs. TL;DR: If the FreeBSD project wants help, ask. When I read the quarterly status reports, I notice the number of open PRs f= or base and ports. If that section asked for help in triaging bugs, I would ha= ve volunteered. As an example, volunteers could go through open bug reports and just look for ones filed on (now) unsupported FreeBSD versions, and reply to those PRs with "Is anyone still encountering this issue on a currently-supported version of FreeBSD?". I expect that there will be some = "no" answers as well as "nobody home" after (for example) 60 days and the bugs c= an be closed with "Overcome by events". This should drop the number of open PR= s by a good amount, with almost no work by any committer beyond what's mentioned= in the next paragraph. That work doesn't require any privileges beyond just having a Bugzilla acco= unt as long as there's someone or an alias who can take a list of PR numbers generated by this volunteer work and close bugs as appropriate. That probab= ly involves some additional work by the person with modify privileges in Bugzi= lla to make sure the bugs requesting to be closed are actually the right ones (= in case of typos). That should just involve looking at the most recent comment posted by either the submitter or the volunteer reviewer. In the case of this particular PR, I looked at the code before I submitted = the PR, and at the time I couldn't see anything that I was comfortable submitti= ng a patch for. In some other bugs, I've submitted patches, most of which have been accepte= d. Lastly, thanks for responding. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206360-227-09MSdjFFdn>