public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: acpi-support-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [ACPI-sppt] ACPI bug databases
Date: 03 Oct 2003 00:56:04 -0400	[thread overview]
Message-ID: <1065156964.5326.177.camel@dhcppc4> (raw)

A reminder...

All Linux Kernel (both 2.4 and 2.6) bugs related to ACPI should go here:
http://bugzilla.kernel.org/
Category: Power Management
Component: ACPI

If the bug is specific to a distro, please put it there:
http://bugzilla.redhat.com
http://bugzilla.suse.de/
or whereever.

As the distros don't use the component=ACPI scheme, please be encouraged
to add "linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org" to the CC: list.  That will help us find
it -- not because I can keep up on e-mail, but because it makes for a
simple bugzilla query;-)

thanks,
-Len

ps. I discovered the ACPI Tracker on sourceforge.net had somehow
re-enabled itself, so I disabled it again.  If that is a hardship for
anybody, please let me know.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

             reply	other threads:[~2003-10-03  4:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03  4:56 Len Brown [this message]
     [not found] ` <1065156964.5326.177.camel-D2Zvc0uNKG8@public.gmane.org>
2003-10-11  0:10   ` [ACPI-sppt] ACPI bug databases Sérgio Monteiro Basto
     [not found]     ` <1065831018.1500.3.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-10-11  0:33       ` Sérgio Monteiro Basto
     [not found]         ` <1065832414.1498.25.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2003-10-11  4:48           ` Len Brown

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=1065156964.5326.177.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=acpi-support-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