Date: Fri, 01 Dec 2017 12:15:21 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Kristof Provost" <kp@FreeBSD.org> Cc: "Mike Remski" <mremski@comcast.net>, freebsd-hackers@freebsd.org, Dieter BSD <dieterbsd@gmail.com>, freebsd-arch@freebsd.org Subject: Re: Getting PRs fixed [ was: Re: The future of fortune(6) ] Message-ID: <3894.1512130521@critter.freebsd.dk> In-Reply-To: <C8FB6D11-043A-4F62-BEE4-B95DDD3F35A4@FreeBSD.org> References: <CAA3ZYrCCQPeSk4EvL=VN06R8C_FHkXmj%2BSor46t2sWPjzJTbJg@mail.gmail.com> <1306478885.37537.1512123855297@connect.xfinity.com> <C8FB6D11-043A-4F62-BEE4-B95DDD3F35A4@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <C8FB6D11-043A-4F62-BEE4-B95DDD3F35A4@FreeBSD.org>, "Kristof Pr= ovost" writes: >Good bug reports are enormously valuable. A bug report with a clear = >reproduction scenario is vastly more likely to get fixed (quickly). In the Varnish Cache project I have set a very clear policy for bugreports: If they are not actionable (after interacting with the submitter), we close them, even if they are indicative of a bug. A bugreport which says "Crash under circumstances unknown" has no value for the developers. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3894.1512130521>