From owner-freebsd-hackers@freebsd.org Fri Jun 1 15:13:47 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 9D805EFDEC3 for ; Fri, 1 Jun 2018 15:13:47 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 284B6812AB for ; Fri, 1 Jun 2018 15:13:47 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: 5c972bf1-65ae-11e8-8837-614b7c574d04 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 5c972bf1-65ae-11e8-8837-614b7c574d04; Fri, 01 Jun 2018 15:13:39 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w51FDcBk026270; Fri, 1 Jun 2018 09:13:38 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1527866018.32688.195.camel@freebsd.org> Subject: Re: PRs are being closed for bogus reasons :-( From: Ian Lepore To: rb@gid.co.uk Cc: "freebsd-hackers@freebsd.org" Date: Fri, 01 Jun 2018 09:13:38 -0600 In-Reply-To: References: <1407.1527801278@critter.freebsd.dk> Content-Type: text/plain; charset="iso-8859-7" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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 15:13:47 -0000 On Fri, 2018-06-01 at 15:53 +0100, rb@gid.co.uk wrote: > > > > On 1 Jun 2018, at 15:41, Warner Losh wrote: > > > > > > > > On Fri, Jun 1, 2018 at 8:10 AM, Bob Bishop wrote: > > > Hi, > > > > > > > > > > > On 31 May 2018, at 22:14, Poul-Henning Kamp wrote: > > > > > > > > -------- > > > > In message > > > > , Warner Losh writes: > > > > > > > > > > > > > > There's a problem with the PR database: there's too many bugs. > > > > And despite the valiant efforts of a number of people over the > > > > lifetime of the project, it has always had so many bugs that > > > > everybody just threw their hands in the air and walked away. > > > > > > > > The way to improve the situation is to fix PR's, not to complain > > > > about PRs. > > > Indeed. But look at the number of PRs with patches that are stuck in that state. Not pretty. > > Over the years I've committed dozens of PRs that had patches in them. The sad truth is that only about 10-15% of them have comitable patches in them when submitted. And that number decays over time as things age in bugzilla. [etc] > Sure. But the best a non-comitter can do is to supply a patch tested against HEAD. If the patch rots because it hasn¢t been committed six months down the line it¢s not my fault. > The problem isn't bitrot, the problem is that many patches amount to "here's a hack that works for me," and that isn't necessarily committable. A committer typically has to do almost as much work to figure out whether the patch is appropriate for all users on all arches as they would have to do to develop a fix from scratch. Even if the submitter has mad skills and submits a perfect patch, better than what the committer would have done from scratch, the work to analyze everything and decide whether that's the case still has to be done. -- Ian