From: "David Poehlman" <poehlman1@comcast.net>
To: <speakup@braille.uwo.ca>
Subject: Re: NFB Net goes linux!
Date: Sat, 21 Sep 2002 17:39:28 -0400 [thread overview]
Message-ID: <000b01c261b7$5d09ada0$1cf42041@inspiron5000e> (raw)
In-Reply-To: <001201c261b2$d605ea20$6f11ba3f@rgallegos>
yes, because they deserve bashing.
----- Original Message -----
From: "Raul A. Gallegos" <raul@asmodean.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, September 21, 2002 5:07 PM
Subject: Re: NFB Net goes linux!
Does everything have to be turned into an nfb bashing session?
--
If you perceive that there are four possible ways in which a procedure
can
go wrong, and circumvent these, then a fifth way will promptly develop.
----- Original Message -----
From: "Ann Parsons" <akp@eznet.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, September 21, 2002 5:53 AM
Subject: Re: NFB Net goes linux!
> Hi all,
>
> Well, now, old Buddy, one would think that his motives would be fueled
> by logic. If one were going to buy or be given apparatus for
> maintaining the email lists, web and so on of an organization, one
> would desire the best equipment, but one would also make sure that it
> was configurable by those who were going to use it. It makes no sense
> to have equipment in one's office that one can not configure by
> oneself. Even if the learning curve were steep, it would make sense
> that any equipment should be flexible enough to be configured by the
> blind and not the sighted. But then, who ever said members of that
> organization thought logically or had a modicum of common sense?
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0209200740230.1232-100000@tasha-yar.dorsai.o rg>
` Charles Crawford
` Ann Parsons
` Paul Migliorelli (+1 3 0 3 5 4 3 2 3 1 1)
` Ann Parsons
` Alex Snow
` Ryan Mann
` Scott B. Berry
` Ann Parsons
` Scott Howell
` Ann Parsons
` Steve Holmes
` Scott Howell
` Darrell Shandrow
` David Poehlman
` Darrell Shandrow
` Why I choose Linux, was " Kenny Hitt
` Darrell Shandrow
` Janina Sajka
` Alex Snow
` Bear in SFO
` OCR -- Was "Why I Choose Linux" Janina Sajka
` Gregory Nowak
` Janina Sajka
` Gregory Nowak
` Scott Howell
` Adam Myrow
` Janina Sajka
` Kenny Hitt
` NFB Net goes linux! Ann Parsons
` Darrell Shandrow
` Raul A. Gallegos
[not found] ` <15757.3213.253849.328221%akp@eznet.net>
` David Poehlman
` Bear in SFO
` David Poehlman
` Bear in SFO
` Darrell Shandrow
` Ann Parsons
` Alex Snow
` Scott B. Berry
` Ann Parsons
` Ann Parsons
` Zinf command line ccrawford
` Steve Holmes
` Steve Holmes
` ccrawford
` Steve Holmes
` ccrawford
` Steve Holmes
` Janina Sajka
` Deedra Waters
` ccrawford
` Deedra Waters
` ccrawford
` NFB Net goes linux! Ann Parsons
` Ann Parsons
` Buddy Brannan
` Erik Heil
` Scott Howell
` Darrell Shandrow
` Alex Snow
` Darrell Shandrow
` Ann Parsons
` Raul A. Gallegos
` David Poehlman [this message]
` Ann Parsons
` Alex Snow
` Scott Howell
` Ann Parsons
` Alex Snow
` Mitchell Smith
` Darrell Shandrow
` David Poehlman
Patricia Logan
` Alex Snow
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='000b01c261b7$5d09ada0$1cf42041@inspiron5000e' \
--to=poehlman1@comcast.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).