From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] History of man pages
Date: Tue, 31 Jan 2012 12:36:31 +1100 [thread overview]
Message-ID: <20120131013631.GB45125@dereel.lemis.com> (raw)
I've received a link http://manpages.bsd.lv/history.html claiming to
be about man pages; in fact, it's a lot more than that, including the
prehistory of troff. Interesting stuff.
Greg
--
Sent from my desktop computer
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20120131/ecd35fb0/attachment.sig>
next reply other threads:[~2012-01-31 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 1:36 Greg 'groggy' Lehey [this message]
2012-01-31 1:53 ` Warren Toomey
2012-01-31 13:04 ` Ronald Natalie
2012-01-31 15:49 ` Larry McVoy
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=20120131013631.GB45125@dereel.lemis.com \
--to=grog@lemis.com \
/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).