From: Derek Broughton <dbroughton-F3m4/jXepmf3fQ9qLvQP4Q@public.gmane.org>
To: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: making progress with ACPI was: ACPI small patch update (20021024)
Date: Tue, 29 Oct 2002 08:20:37 -0400 [thread overview]
Message-ID: <005401c27f45$967de820$3746028e@bio.dfo.ca> (raw)
In-Reply-To: 20021028213404.U27461@parcelfarce.linux.theplanet.co.uk
From: "Matthew Wilcox" <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
> On Mon, Oct 28, 2002 at 10:16:04PM +0100, Martin Waitz wrote:
> > On Mon, Oct 28, 2002 at 09:31:10PM +0100, joerg.beyer-htSm2yLGOjU@public.gmane.org wrote:
> > > well sourceforge gives you a bug tracker, if you want it.
> >
> > ibm talked about sponsoring a bugzilla for kernel development.
> > perhaps one could use that for acpi, too.
>
> i find it fascinating that there are so many people on this list who want
> to see a bug tracking system, but don't feel able to keep a list of bugs
> themselves. why is that? expecting andy to set it up seems unreasonable.
What could possibly be gained by everybody keeping independent bug lists?
Nobody expects Andrew to do it, but Andrew seems opposed to the idea of _having_
a bug tracker - even if somebody else does it. Consider that if I was keeping
my own "bug list" it would have exactly one bug - and it wouldn't be an ACPI
problem, it would be the lousy DSDT on this Dell Inspiron. Everything that my
DSDT properly defines, ACPI handles well.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-29 12:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 20:31 making progress with ACPI was: ACPI small patch update (20021024) joerg.beyer-htSm2yLGOjU
[not found] ` <200210282031.g9SKVAX06731-pb599fR3TxVkExQqqHjIK3sFFmKitW5W@public.gmane.org>
2002-10-28 21:16 ` Martin Waitz
[not found] ` <20021028211603.GD1402-4e/A4rHm86X2JYTphGNI2Q@public.gmane.org>
2002-10-28 21:34 ` Matthew Wilcox
2002-10-29 12:20 ` Derek Broughton [this message]
[not found] ` <005401c27f45$967de820$3746028e-dP0OE4Ef7fWw5LPnMra/2Q@public.gmane.org>
2002-10-29 14:02 ` Matthew Wilcox
[not found] ` <20021028213404.U27461-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2002-10-29 12:43 ` Aaron Gaudio
[not found] ` <20021029124329.GA25692-2LEdZMXKCZJeeLb3ft/vUmD2FQJk+8+b@public.gmane.org>
2002-10-29 14:03 ` Matthew Wilcox
2002-10-28 21:38 ` kneumann-4bfl1RV3iZDOEhgYWvzSCYQuADTiUCJX
-- strict thread matches above, loose matches on Subject: below --
2002-10-29 7:30 Jens Haug
[not found] ` <200210290730.g9T7UDD26513-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-10-29 10:45 ` Mark Pritchard
2002-10-28 20:02 Nakajima, Jun
2002-10-28 19:20 Grover, Andrew
[not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A476-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-01-16 19:53 ` Pavel Machek
2002-10-28 19:56 ` Alan Cox
2002-10-29 2:30 ` J
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='005401c27f45$967de820$3746028e@bio.dfo.ca' \
--to=dbroughton-f3m4/jxepmf3fq9qlvqp4q@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox