From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] [hangar18-general] Introduction (fwd)
Date: Wed, 28 Jan 2004 03:46:18 +0100 [thread overview]
Message-ID: <040f01c3e54a$2ceb8900$67844051@SOMA> (raw)
In-Reply-To: <401693F9.9030907@linuxlink.com>
yeah, i was on crack and thought i'd cripple my LA-120s to 300 baud,
but i could still use sam -d ...
that's what i call progress or was it just the crack?
prev parent reply other threads:[~2004-01-28 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 3:43 Jim Choate
2004-01-27 4:33 ` boyd, rounin
2004-01-27 11:00 ` Bruce Ellis
2004-01-27 16:38 ` Michael H. Collins
2004-01-28 2:46 ` boyd, rounin [this message]
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='040f01c3e54a$2ceb8900$67844051@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).