From: Greg Earle earle@isolar.Tujunga.CA.US
Subject: SCSI recommendations?
Date: Thu, 2 May 1996 19:31:58 -0400 [thread overview]
Message-ID: <19960502233158.PKAN4DVadPNLK6Je2cbDO7XjA6sKAJe4qVtnwoS6kjU@z> (raw)
Jim McKie writes:
> It's unlikely there will ever be an Adaptec 29xx driver.
Surely someone could take the supposedly-rock-solid FreeBSD-current 2940
driver and port it (or use it as a base)?
> ------ forwarded message follows ------
>
> >From cse.psu.edu!9fans-outgoing-owner Thu May 2 12:53:52 EDT 1996
> Received: from colossus.cse.psu.edu by plan9; Thu May 2 12:53:52 EDT 1996
> [...]
There's something immensely humorous/ironic about the Plan 9 mail program
apparently commiting the heinous newbie offense of including the entire
message being responded to (headers and all), and *after* the followup. :-)
(cc:Mail is bad enough for this kind of thing, but ... )
- Greg
next reply other threads:[~1996-05-02 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-02 23:31 Greg [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-05-07 7:09 Nigel
1996-05-03 1:19 jim
1996-05-02 21:07 Geoff
1996-05-02 17:35 Nickolay
1996-05-02 16:05 Martin
1996-05-02 16:01 jim
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=19960502233158.PKAN4DVadPNLK6Je2cbDO7XjA6sKAJe4qVtnwoS6kjU@z \
--to=9fans@9fans.net \
/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).