From: Jeff Garzik <jgarzik@pobox.com>
To: Len Brown <len.brown@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0 (ACPI)
Date: Thu, 18 Dec 2003 03:05:00 -0500 [thread overview]
Message-ID: <3FE15FAC.70300@pobox.com> (raw)
In-Reply-To: <1071734123.2497.66.camel@dhcppc4>
Len Brown wrote:
>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix/should-fix-7.txt
>
>
> We have 88 open bugs against ACPI (out of 216 total). They fall into
> two broad categories -- boot/configuration (eg. interrupt issues); and
> run-time features (eg. acpi events -- power-down, fan control etc).
> #1038 mentioned here has sort of grown out of control into "anything at
> all wrong with anybody's IBM T40", so I'm not sure it will ever be
> completely closed;-)
hehe
Pete Zaitcev gave me some great advice, when I joined Red Hat. Manage
your bugs aggressively, sometimes with a sharp and pointy stick.
Otherwise they will become unkillable nine-headed hydra with a life of
their own, as the bugs drift further and further away from the original
bug reporter's bug. ;-) Open new bugs if a poster's issue seems
remotely different from the base bug. Bugzilla can do fancy stuff like
linking bugs into dependency chains, and also marking bugs as
duplicates. The power is yours :)
Jeff
next prev parent reply other threads:[~2003-12-18 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE001B57534@hdsmsx402.hd.intel.com>
2003-12-18 7:55 ` Linux 2.6.0 (ACPI) Len Brown
2003-12-18 8:05 ` Jeff Garzik [this message]
2003-12-18 8:12 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FE15FAC.70300@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.