From owner-freebsd-hackers@freebsd.org Fri Jun 1 20:17:11 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 472B7F74AA1 for ; Fri, 1 Jun 2018 20:17:11 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86D5071350; Fri, 1 Jun 2018 20:17:10 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 5FEA35A9F12; Fri, 1 Jun 2018 20:17:09 +0000 (UTC) Date: Fri, 1 Jun 2018 20:17:09 +0000 From: Brooks Davis To: Conrad Meyer Cc: "Andrey V. Elsukov" , "freebsd-hackers@freebsd.org" Subject: Re: PRs are being closed for bogus reasons :-( Message-ID: <20180601201709.GD29648@spindle.one-eyed-alien.net> References: <20180531210212.GD24090@lonesome.com> <5f84bfc4-3e47-283f-184f-49df94e0d457@yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZmUaFz6apKcXQszQ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2018 20:17:11 -0000 --ZmUaFz6apKcXQszQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 01, 2018 at 11:23:48AM -0700, Conrad Meyer wrote: > On Fri, Jun 1, 2018 at 2:09 AM, Andrey V. Elsukov wro= te: > > On 01.06.2018 00:02, Mark Linimon wrote: > >> I'd like to see us do a lot better at dealing with "PRs with patches" = -- > >> even more so than "can't get FreeBSD to run" -- but without some kind > >> of set of new volunteers willing to work on only such issues, it simply > >> isn't going to happen. > > > > I suggest to forcibly subscribe any committers to the freebsd-bugs@ > > mailing list in addition to *-committers@. :) >=20 > Hi Andrey, >=20 > Maybe this proposal was made in jest, but I actually like the idea. > The dominant noise of freebsd-bugs@ comes from follow-up comments, bug > status notifications (sometimes bulk changes made by e.g., Eitan), or > direct email reply discussion (not really sure why bugs@ isn't just > treated as announce-only). >=20 > It's still sort of a firehose if you *just* receive new bug reports, > but it's much more manageable and you can click through any that look > interesting and mark the rest read with no risk of future > notification. +1 I did a bit of triage while skimming the resets Eitan did and while I didn't find much actionable I was able to close some things properly. -- Brooks --ZmUaFz6apKcXQszQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbEanEAAoJEKzQXbSebgfAHNMH/j0Si9Qy5hO0sVNdxDYZOZX+ VmJngJOCBUhImLH2yqnCdnddOjRt0o+CflvcjDv6XPXNS4PjMOr5N6+PP4/YiBhK pLicZp5klD1hepbvtmLX0XGG9yl45uBiJ/NpAuxWMM//dR3OpxuRFUhrzB7B2TKH 0pqD71WVUivC7eInVTBQcv5B96S7zzlkYUvRVHKn9Vxqqy0RK1JgXOLi8aXiaHu7 G0Odbw/XJyhNDYiBI10riG19nHE0W2MSDYgLcO3HjVKdnUTBCxEZqtKsvG63sBli 9AD7UsxB8Z9D9wBJRarw0g1SnSUoMaiAPOp9fGT2quuQobW2Ye3gklomug+Rkt8= =x+mf -----END PGP SIGNATURE----- --ZmUaFz6apKcXQszQ--