From: tony seth <lp800@samobile.net>
To: speakup@braille.uwo.ca
Subject: Re: pc weasel?
Date: Sun, 16 Jan 2011 12:50:43 -0500 [thread overview]
Message-ID: <20110116175043.2453.9189@domU-12-31-38-07-3C-65.compute-1.internal> (raw)
Yes please... just let me know the particulars off list...
My e-mail is:
lp800@samobile.net
Thanks much and have a groovy day.
Cheereo!
--
Email services provided by the System Access Mobile Network. Visit
www.serotek.com to learn more about accessibility anywhere.
next reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
tony seth [this message]
-- strict thread matches above, loose matches on Subject: below --
tony seth
[not found] <Pine.BSF.4.64.1101132219100.52517@server1.shellworld.net>
[not found] ` <20110114070444.GA10605@football.tbsaunde.org>
[not found] ` <Pine.BSF.4.64.1101140215240.64994@server1.shellworld.net>
[not found] ` <alpine.DEB.2.00.1101151616420.3293@data.home>
` Mike Keithley
tony seth
` John G. Heim
tony seth
` John Heim
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=20110116175043.2453.9189@domU-12-31-38-07-3C-65.compute-1.internal \
--to=lp800@samobile.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).