Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 Jun 2018 20:17:09 +0000
From:      Brooks Davis <brooks@freebsd.org>
To:        Conrad Meyer <cem@freebsd.org>
Cc:        "Andrey V. Elsukov" <bu7cher@yandex.ru>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
Subject:   Re: PRs are being closed for bogus reasons :-(
Message-ID:  <20180601201709.GD29648@spindle.one-eyed-alien.net>
In-Reply-To: <CAG6CVpXk8RsopZgJ41x1n3uOTir5gVykthPYJAhCyTn-CwsCPQ@mail.gmail.com>
References:  <CAA3ZYrDE1qN36jkg6bfTuUQL-Ko01UhVa=i%2BJ7t7AfN4hdBDMQ@mail.gmail.com> <20180531210212.GD24090@lonesome.com> <5f84bfc4-3e47-283f-184f-49df94e0d457@yandex.ru> <CAG6CVpXk8RsopZgJ41x1n3uOTir5gVykthPYJAhCyTn-CwsCPQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--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 <bu7cher@yandex.ru> 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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180601201709.GD29648>