rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: <dws@ssec.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Plan 9 Programmer's Manual available for FTP
Date: Wed, 14 Oct 1992 23:05:13 -0400	[thread overview]
Message-ID: <9210150305.AA20849@ssec.ssec.wisc.edu> (raw)

Straight from comp.os.research:

From: rob@research.att.com (Rob Pike)
Newsgroups: comp.os.research
Subject: Plan 9 Manual now available by FTP
Date: 14 Oct 92 19:27:55 GMT
Organization: AT&T Bell Laboratories, Murray Hill NJ
Lines: 7
Approved: comp-os-research@ftp.cse.ucsc.edu
Message-ID: <1bib2aINNmgu@darkstar.UCSC.EDU>
NNTP-Posting-Host: ftp.cse.ucsc.edu
Originator: osr@ftp

The Programmer's Manual and supporting documentation for
Plan 9 from Bell Labs is now available by anonymous FTP
from research.att.com, directory dist/plan9man.

Rob Pike
rob@research.att.com


             reply	other threads:[~1992-10-15  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-10-15  3:05 dws [this message]
1992-10-15  3:19 Jim Davis

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=9210150305.AA20849@ssec.ssec.wisc.edu \
    --to=dws@ssec.wisc.edu \
    --cc=rc@hawkwind.utcs.toronto.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).