From: Vince Herried <vherried-rEckef8uG3NTGrOy2lmfZw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: doc on ACPI
Date: Fri, 14 Feb 2003 10:27:58 +0000 [thread overview]
Message-ID: <200302141027.58053.vherried@insight.rr.com> (raw)
re doc on acpi... Possibly no good for this level???
Intel has a book on it. Haven't read through it all yet...
isbn -09702846-8-3
"Building the Poser-Efficient PC,
a developer's Guide to ACPI Power Management"
They suggest
http://www.intel.com/intelpress
--
Rules for Good Grammar #4.
(1) Don't use no double negatives.
(2) Make each pronoun agree with their antecedents.
(3) Join clauses good, like a conjunction should.
(4) About them sentence fragments.
(5) When dangling, watch your participles.
(6) Verbs has got to agree with their subjects.
(7) Just between you and i, case is important.
(8) Don't write run-on sentences when they are hard to read.
(9) Don't use commas, which aren't necessary.
(10) Try to not ever split infinitives.
(11) It is important to use your apostrophe's correctly.
(12) Proofread your writing to see if you any words out.
(13) Correct speling is essential.
(14) A preposition is something you never end a sentence with.
(15) While a transcendant vocabulary is laudable, one must be eternally
careful so that the calculated objective of communication does not
become ensconsed in obscurity. In other words, eschew obfuscation.
Vince
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
reply other threads:[~2003-02-14 10:27 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=200302141027.58053.vherried@insight.rr.com \
--to=vherried-reckef8ug3ntgroy2lmfzw@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