public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: John Summerfield <summer-bdq14YP6qtSeVB85EesmETSf8X3wrgjD@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: making progress with ACPI was: ACPI small patch update
Date: Thu, 31 Oct 2002 09:43:15 +0800	[thread overview]
Message-ID: <200210310940.17218.acpi@computerdatasafe.com.au> (raw)
In-Reply-To: <200210300925.g9U9PbD05581-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>

Rats. Did it again.

On Wed, 30 Oct 2002 17:25, Jens Haug wrote:
> Or maybe people will read about all these bugs and think ACPI on
> Intel was a mess - although these bugs are perfectly normal in this
> stage of development.
> I dunno.
> Maybe I'm all wrong here. I hope I am.

Does the lk team hide its bugs?

To my mind the best-supported software I use is fetchmail, and the standard 
way there of reporting bugs is to the list. It's very public.

Red Hat's buglist is open to all, for all the software it packages. I expect 
ACPI falls between the two in the number of bugs it has.


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en

  parent reply	other threads:[~2002-10-31  1:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  9:25 Re: making progress with ACPI was: ACPI small patch update Jens Haug
2002-10-30  9:29 ` Valette Eric
     [not found] ` <200210300925.g9U9PbD05581-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-10-30  9:44   ` Markus Gaugusch
2002-10-31  1:43   ` John Summerfield [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31  7:21 Jens Haug
2002-10-30  7:12 Jens Haug
2002-10-30  9:06 ` Valette Eric
2002-10-30 12:50 ` Derek Broughton
     [not found] ` <200210300712.g9U7CFD04441-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-10-30 16:18   ` Randy.Dunlap
2002-10-31  1:36   ` John Summerfield
     [not found] <E186Vl0-0005aM-00@usw-sf-list2.sourceforge.net>
2002-10-29 18:23 ` Huw Hawkins
     [not found]   ` <m2d6pure9h.fsf@tnuctip.rychter.com>
2002-10-29 22:29     ` Valette Eric

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=200210310940.17218.acpi@computerdatasafe.com.au \
    --to=summer-bdq14yp6qtsevb85eesmetsf8x3wrgjd@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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