From owner-freebsd-hackers@freebsd.org Fri Jun 1 10:55:27 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 24E5FEFD8C4 for ; Fri, 1 Jun 2018 10:55:27 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C854E74803; Fri, 1 Jun 2018 10:55:26 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 1654EE8C; Fri, 1 Jun 2018 05:55:26 -0500 (CDT) Date: Fri, 1 Jun 2018 05:55:25 -0500 From: Mark Linimon To: Eugene Grosbein Cc: Dieter BSD , freebsd-hackers@freebsd.org, linimon@FreeBSD.org Subject: Re: PRs are being closed for bogus reasons :-( Message-ID: <20180601105524.GE25691@lonesome.com> References: <5B111DA3.7020503@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5B111DA3.7020503@grosbein.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailman-Approved-At: Fri, 01 Jun 2018 11:40:45 +0000 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 10:55:27 -0000 On Fri, Jun 01, 2018 at 05:19:15PM +0700, Eugene Grosbein wrote: > Not every PR describes real problem. What is exact PR number you > are referring to? There were several in 'Base System'/'amd64' that described boot and install problems during the FreeBSD 8/9/10 timeframes, and did seem like they were (or at least had been) legitimate problems. My personal feeling is that if such things don't get addressed within a release timeframe, it's likely that either a) the problem was fixed later or b) the submitter gave up and went on to some other hardware or even OS. Obviously this was not Dieter BSD's experience. I'm sorry about that but I am not personally in a position to work through all the e.g. boot/install problems that come in. The number is so overwhelming that they rarely get handled in a timely fashion (the "trying to drink from a firehose" problem). Referring people to the forums, or IRC, for such things seems a little unsatisfying as well. I also apologize for the boilerplate response, which several people just found rude. Let's see if we can come up with a better one. tl:dr; there are too many PRs. mcl