From owner-freebsd-hackers@freebsd.org Fri Dec 1 12:15:48 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD5B7DFEF15; Fri, 1 Dec 2017 12:15:48 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 9244C7F882; Fri, 1 Dec 2017 12:15:47 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id EB7912739B; Fri, 1 Dec 2017 12:15:37 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id vB1CFMcI003896 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 1 Dec 2017 12:15:22 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id vB1CFLbb003895; Fri, 1 Dec 2017 12:15:21 GMT (envelope-from phk) To: "Kristof Provost" cc: "Mike Remski" , freebsd-hackers@freebsd.org, Dieter BSD , freebsd-arch@freebsd.org Subject: Re: Getting PRs fixed [ was: Re: The future of fortune(6) ] In-reply-to: From: "Poul-Henning Kamp" References: <1306478885.37537.1512123855297@connect.xfinity.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3893.1512130521.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Fri, 01 Dec 2017 12:15:21 +0000 Message-ID: <3894.1512130521@critter.freebsd.dk> X-Mailman-Approved-At: Fri, 01 Dec 2017 16:55:21 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 12:15:48 -0000 -------- In message , "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= .