From: cpt.kirk@1tree.net
To: speakup@braille.uwo.ca
Subject: Re: need comments
Date: Tue, 28 Mar 2000 10:10:29 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.10.10003280955580.1677-100000@rocky> (raw)
In-Reply-To: <Pine.LNX.4.10.10003280942540.30416-100000@mud.blinksoft.com>
Kirk,
I don't know if this is a workable idea or not. What if it probed like it
does now. If it finds something definative it goes no further, but if it
does not find something definative, it guesses at ports based on the CTS
line status. I apologize if this isn't feasable.
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Your fly might be open (but don't check it just now).
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Kirk Reiser
` Whistler
` Kirk Reiser
` Whistler
` cpt.kirk [this message]
` Buddy Brannan
` Christopher Moore
` Kirk Reiser
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=Pine.LNX.4.10.10003280955580.1677-100000@rocky \
--to=cpt.kirk@1tree.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).