From owner-freebsd-bugbusters@FreeBSD.ORG Fri Jan 25 19:37:19 2008 Return-Path: Delivered-To: freebsd-bugbusters@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4597716A41B for ; Fri, 25 Jan 2008 19:37:19 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 146CA13C467 for ; Fri, 25 Jan 2008 19:37:18 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 46611 invoked from network); 25 Jan 2008 19:37:19 -0000 Received: from adsl-71-141-123-117.dsl.snfc21.pacbell.net (HELO ?192.168.1.77?) (nate-mail@71.141.123.117) by root.org with ESMTPA; 25 Jan 2008 19:37:19 -0000 Message-ID: <479A3A67.5070401@root.org> Date: Fri, 25 Jan 2008 11:37:11 -0800 From: Nate Lawson User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Mark Linimon References: <20080125183914.GC21911@soaustin.net> <479A2F84.5060707@root.org> <20080125192729.GA3521@soaustin.net> In-Reply-To: <20080125192729.GA3521@soaustin.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugbusters@FreeBSD.org Subject: Re: upcoming bugathon this weekend X-BeenThere: freebsd-bugbusters@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Coordination of the Problem Report handling effort." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 19:37:19 -0000 Mark Linimon wrote: > On Fri, Jan 25, 2008 at 10:50:44AM -0800, Nate Lawson wrote: >> Thanks for doing this. If you go through bugs owned by freebsd-acpi@, >> I'll try to respond to any questions via email. > > One of the idle thoughts we had was just to create an acpi category, > and thus the auto-assigner will do some work for us. Since you're > doing most of the work on acpi, what do you think? Ok by me. The only problem I have is that a lot of people blame acpi when it's really a driver problem. The best acid test is to boot with acpi disabled and show the feature works whereas with it enabled, it fails. -- Nate