From owner-freebsd-stable Sun Sep 17 2:52:43 2000 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 2646737B422; Sun, 17 Sep 2000 02:52:39 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8H9qX608147; Sun, 17 Sep 2000 02:52:33 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: freebsd-stable@FreeBSD.ORG Cc: stable@FreeBSD.ORG, cg@FreeBSD.ORG, dg@FreeBSD.ORG Subject: In summary.. [Re: I'll be rolling a 4.1.1 release on September 25th] In-Reply-To: Message from Peter Radcliffe of "Sat, 16 Sep 2000 18:07:37 EDT." <20000916180737.B2124@pir.net> Date: Sun, 17 Sep 2000 02:52:33 -0700 Message-ID: <8143.969184353@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can we _please_ get these two patches into at least -stable before or > after this release cut ? > > Many of us have been using them for months and they make the built in > ether and sound work through a suspend/resume on my laptop; > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18756 > http://www.freebsd.org/cgi/query-pr.cgi?pr=20255 Well, I read this whole thread through, with all the various comments from Kris and Garance [among others], and then I decided to go look at the two PRs in question just to see what all the fuss was about. It turns out that both of these are actually fairly straight-forward to deal with in that they've been specifically assigned to individual developers and publically marked as such. PR#18756 is an fxp driver issue and, as marked, clearly the domain of David Greenman given that nobody other than him would likely even dare commit a change to the fxp driver lest they get flamed for their presumption. :-) PR#20255 has been assigned to Cameron Grant, the maestro of the audio drivers, and it's highly unlikely that anyone other than he would even know if the supplied patches were correct. In both cases, you're essentially now blocking on a single developer and it's up to those two developers to come out of the woodwork and either adopt or close these PRs as incorrect (given some justification, of course). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message