From: "Michael H. Collins" <mike@linuxlink.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [hangar18-general] Introduction (fwd)
Date: Tue, 27 Jan 2004 10:38:17 -0600 [thread overview]
Message-ID: <401693F9.9030907@linuxlink.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0401262143170.25637-100000@einstein.ssz.com>
Schweeet.
Jim Choate wrote:
>
> ---------- Forwarded message ----------
> Date: Mon, 26 Jan 2004 13:33:06 -0700
> From: Brad Davis <brad@peakunix.net>
> Reply-To: hangar18-general@open-forge.org
> To: hangar18-general@open-forge.org
> Subject: [hangar18-general] Introduction
>
> Hi,
>
> Some time ago, I bought a PC with Windows 95 for the purpose of
> doing some on line trading. The computer soon became more
> fascinating to me than the stock market. However, I became
> increasingly frustrated with the limits imposed on me by the OS.
>
--
Michael H. Collins Admiral, Penguinista Navy
http://linuxlink.com
http://www.honestvaclavs.com/
next prev parent reply other threads:[~2004-01-27 16:38 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 [this message]
2004-01-28 2:46 ` boyd, rounin
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=401693F9.9030907@linuxlink.com \
--to=mike@linuxlink.com \
--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).