From: "Derek Broughton" <dbroughton-TXp3Tk8lDUJBDgjK7y7TUQ@public.gmane.org>
To: acpi-support-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [ACPI-sppt] Re: [ACPI] merge acpi-support into acpi-devel?
Date: Fri, 3 Oct 2003 16:42:32 +0100 [thread overview]
Message-ID: <002f01c389c5$047efe60$f801dc0a@direcway.com> (raw)
In-Reply-To: 1065155697.5326.134.camel@dhcppc4
From: "Len Brown" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> It would make my life simpler if acpi-suport-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org were
> merged into acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org and then disabled.
>
> Does having two lists make life simpler for anybody?
It would if acpi-devel weren't a de-facto support list. If acpi-devel was
really just for developers, I'd just subscribe to acpi-support (which I may
do anyway, since I finally have a complete acpi implementation for my
Inspiron 2500 with kernel 2.4.22). So far, I've been able to offer a little
advice to people on acpi-support, but everything that has helped _me_ I got
from acpi-devel.
So, unless somebody takes it upon themselves to tell every person who asks a
support-type question on acpi-devel to post on the correct list, I'd say
there's not much point for the separation.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-10-03 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 4:34 [ACPI-sppt] merge acpi-support into acpi-devel? Len Brown
2003-10-03 15:42 ` Derek Broughton [this message]
[not found] ` <1065155697.5326.134.camel-D2Zvc0uNKG8@public.gmane.org>
2003-10-04 9:27 ` Sérgio Monteiro Basto
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='002f01c389c5$047efe60$f801dc0a@direcway.com' \
--to=dbroughton-txp3tk8ldujbdgjk7y7tuq@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 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.