From: Valette Eric <eric.valette-GANU6spQydw@public.gmane.org>
To: Jens Haug <haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: making progress with ACPI was: ACPI small patch update
Date: Wed, 30 Oct 2002 10:29:27 +0100 [thread overview]
Message-ID: <3DBFA677.5010700@free.fr> (raw)
In-Reply-To: 200210300925.g9U9PbD05581@ikffws2.ikff.uni-stuttgart.de
Jens Haug wrote:
>>I have been working for famous companies and yes having a bug tracking
>>system was required and compled with the source management system.
>
>
> But this wasn't public, was it?
Yes it was unless submitter requested explicitely the contrary.
> No company distributes ACPI for linux.
No but companies are seeling ACPI compatible processors...
-- eric
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-30 9:29 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 [this message]
[not found] ` <200210300925.g9U9PbD05581-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-10-30 9:44 ` Markus Gaugusch
2002-10-31 1:43 ` John Summerfield
-- 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=3DBFA677.5010700@free.fr \
--to=eric.valette-ganu6spqydw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@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.