From: "Thomas D. Ward" <tward1978@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: Re: redHat advanced server 2.0 and speakup
Date: Wed, 16 Apr 2003 16:18:07 -0400 [thread overview]
Message-ID: <004e01c30455$4cf40e60$e0859641@tward1978> (raw)
In-Reply-To: <001601c3042e$91c5ec60$6401a8c0@nu7i>
The problem here is that untrue clames shouldn't be made on the list unless
there is truth to it.
Weather you like Red Hat or not making up false clames gets nowhere, and can
mislead new users into believing Linux is not a viable access solution.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
Don Raikes
` Janina Sajka
` Aaron Howell
` Darrell Shandrow
` Aaron Howell
` Janina Sajka
` Darrell Shandrow
` Janina Sajka
` Darrell Shandrow
` Thomas D. Ward
` Lorenzo Prince
` Janina Sajka
` Thomas Stivers
` Luke Davis
` Thomas Stivers
` Thomas D. Ward [this message]
` Aaron Howell
` Luke Davis
` Lorenzo Prince
` Janina Sajka
` Lorenzo Prince
` Aaron Howell
` Buddy Brannan
` Thomas D. Ward
` Buddy Brannan
` William F. Acker WB2FLW +1-303-722-7209
` Aaron Howell
` Thomas D. Ward
` Janina Sajka
` Darrell Shandrow
` Buddy Brannan
` Aaron Howell
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='004e01c30455$4cf40e60$e0859641@tward1978' \
--to=tward1978@earthlink.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).