From: Malte Thoma <thoma-iYtK5bfT9M8b1SvskN2V4Q@public.gmane.org>
To: jluehr-UIqTAjE4tzc5WgrkcBd8vg@public.gmane.org,
abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@public.gmane.org,
ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org,
faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org,
ACPI-Devel
<Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: heatload
Date: Fri, 20 Dec 2002 08:51:53 +0100 [thread overview]
Message-ID: <3E02CC19.7020208@muenster.de> (raw)
In-Reply-To: <200212171503.03753-UlMRvbVDEoV7PMRmdqgSDxn2srH7JjnQ@public.gmane.org>
Hallo,
if you would like to support me, developing 'heatload' than please
subscirbe to the mailing-list.
Greetings,
Malte
BTW: 'scandir' is on the TODO list, until then the user can adjust the
files via an config-file.
* What about the internel structure of the files in /proc/acpi? Is it
always the same or does it depend on the manufactor, too? That would be
horrible!
* Because my laptop doesn't support FAN and PERFORMANCE, it would be
nice, if someone can send me a 'cat' of those files. Than I can
implement it into heatload.
* If you have a wishlist for me, we can improve heatload to the limits ;-)
https://lists.berlios.de/mailman/listinfo/heatload-general
______________________________________________________________________________
Hallo Ihr,
Ich weiß nicht, ob ich Euch schon angeschrieben hatte:
Bitte trage Euch doch in die meilingliste ein, wenn Ihr mir bei der
Entwicklung von heatload helfen mögt.
Dort erfährt DIhr auch immer wenn es eine neue Version gibt.
Gruß,
Malte
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
parent reply other threads:[~2002-12-20 7:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200212171503.03753-UlMRvbVDEoV7PMRmdqgSDxn2srH7JjnQ@public.gmane.org>]
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=3E02CC19.7020208@muenster.de \
--to=thoma-iytk5bft9m8b1svskn2v4q@public.gmane.org \
--cc=Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
--cc=faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org \
--cc=jluehr-UIqTAjE4tzc5WgrkcBd8vg@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