From owner-freebsd-current@FreeBSD.ORG Sat Jan 12 14:46:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9340C16A417 for ; Sat, 12 Jan 2008 14:46:03 +0000 (UTC) (envelope-from dan@rucci.org) Received: from mta5.srv.hcvlny.cv.net (mta5.srv.hcvlny.cv.net [167.206.4.200]) by mx1.freebsd.org (Postfix) with ESMTP id 5AEA113C442 for ; Sat, 12 Jan 2008 14:46:03 +0000 (UTC) (envelope-from dan@rucci.org) Received: from izer.warganizer.com (ool-182dc652.dyn.optonline.net [24.45.198.82]) by mta5.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JUJ007CIBMHDUP0@mta5.srv.hcvlny.cv.net> for freebsd-current@freebsd.org; Sat, 12 Jan 2008 09:15:53 -0500 (EST) Date: Sat, 12 Jan 2008 09:15:53 -0500 From: Daniel Rucci In-reply-to: <200801111935.50821.peter.schuller@infidyne.com> To: Peter Schuller Message-id: <4788CB99.40305@rucci.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT References: <478556AD.6090400@bsdforen.de> <20080110003524.GB5188@soaustin.net> <200801111935.50821.peter.schuller@infidyne.com> User-Agent: Thunderbird 2.0.0.9 (X11/20080112) X-Mailman-Approved-At: Sat, 12 Jan 2008 15:11:00 +0000 Cc: Mark Linimon , freebsd-current@freebsd.org Subject: Re: Improving the handling of PR:s X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2008 14:46:03 -0000 Peter Schuller wrote: > * The committer may not have access to the hardware, or may not have a > software setup that allows for testing. This means doing such testing > suddenly requires a lot more effort. Would it be possible to identify PRs which are related to specific hardware vs PRs which are not related to hardware? With respect to hardware specific PRs (Since these sound like they can be especially troublesome if the right hardware isn't in the right hands) - user A uploads his dmesg somewhere (if that output is enough) - user A also submits his email address and requests for notifications. - a hardware specific PR & Patch comes in with a committer who doesn't have the necessary hardware to test the patch - user A get a fun email stating the above with instructions on how he/she can help. - user A applys the patch and run the test case or whatever. - user A sends some feedback. - enough of this happens and the committer has more testing behind the patch; the set of all users with this hardware rejoice. Otherwise, I can't see how A can help out with these patches unless they are actively searching gnats for each piece of hardware they have. Meow, Dan