public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: ACPI bugzilla update
Date: 03 Mar 2004 20:22:48 -0500	[thread overview]
Message-ID: <1078363367.12991.386.camel@dhcppc4> (raw)

Because we're such a high-volume customer;-)  ACPI has been promoted out
from under Power Management, up to its own top-level category on
kernel.org bugzilla.  Underneath ACPI are 12 sub-components, split
between configuration, power-management, and issues specific to the AML
interpreter itself:

AML-Interpreter
Config-Interrupts
Config-Procesors
Config-Tables
Config-Tables
Power-Battery
Power-Fan
Power-Off
Power-Procesor
Power-Sleep-Wake
Power-Thermal
Power-Other

The default owners for each comoponent are virtual accounts.
"you can watch any bug's changes that are owned by these accounts by
setting up your 'Users to watch' in Email Settings of your bugzilla
preferences.

We'll set up acpi-bugzilla-5NWGOfrQmneRv+LV9MX5urNAH6kLmebB@public.gmane.org to watch all of them; and
will continue adding that alias to the cc-list for acpi bugs for when
they're owned by somebody else.  If you'd like to get acpi-related
bugzilla e-mail, sign up here:

http://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

If you'd like to just see when new bugs are created and assigned to the
virtual accounts, then watch the owners listed here:

http://bugzilla.kernel.org/describecomponents.cgi?product=ACPI

cheers,
-Len

ps. old PM/ACPI component will be deleted when all the bugs have been
categorized into the new name space.




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

                 reply	other threads:[~2004-03-04  1:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1078363367.12991.386.camel@dhcppc4 \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@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