The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Adam Thornton <athornton@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition
Date: Wed, 20 Sep 2023 02:50:41 +0000	[thread overview]
Message-ID: <weAmWI7k80Qmj5XlXCD5q39caw_2lYfi3Yn-_o3tkOCkisxnzHsgQawVkF3SbMqHk4WNSbc8cOdtUXUS5vWMBefNaJE_fwtRYDgmbY2QGqA=@protonmail.com> (raw)
In-Reply-To: <CAP2nic1oYLQRfn1v81hTOGuJyce68U7Srxu_w+WsATHBrXjSug@mail.gmail.com>

> Yeah, I'm less angry at GNU now--I didn't search as hard, but when I found out 4.3BSD didn't have HISTORY (and neither does 2.11BSD, which is still actively-ish maintained) then I figured it wasn't something classical that GNU dropped, just never imported. I feel like it existed on SunOS and Solaris but I might be wrong about that? Was it really FreeBSD that introduced it?
> 
> Adam

As per my silly bump (really I hate double messages, I'm probably being harder on myself than any of you would be :P) it seems there are some HISTORY sections in the print 4.4BSD set I have on my shelf.  The pages I did spot the section in do not have it in the corresponding 4.3BSD volumes, although I'm basing this on a casual flip through paper books at present, not looking down in /usr/man on any given distro.  None of the Bell-adjacent stuff I've flipped through has any HISTORY sections though.

- Matt G.

  reply	other threads:[~2023-09-20  2:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 20:32 [TUHS] " segaloco via TUHS
2023-09-19 23:39 ` [TUHS] " Larry McVoy
2023-09-20  1:26   ` segaloco via TUHS
2023-09-20  1:30     ` segaloco via TUHS
2023-09-20 14:57       ` Warner Losh
2023-09-20 15:40         ` Dan Cross
2023-09-20  2:09   ` Clem Cole
2023-09-20  2:25     ` Adam Thornton
2023-09-20  2:50       ` segaloco via TUHS [this message]
2023-09-20 19:56       ` Larry McVoy
2023-09-20 20:52         ` segaloco via TUHS
2023-09-20 22:31         ` Dave Horsfall
2023-09-21  4:09           ` Wesley Parish
2023-09-21 13:08             ` John P. Linderman
2023-09-21  0:26         ` Marc Donner
2023-09-21  3:06           ` Adam Thornton
2023-09-21  3:30             ` G. Branden Robinson
2023-09-21  3:48             ` Phil Budne
2023-09-21 13:37         ` Theodore Ts'o
2023-09-20 21:15       ` Alan Coopersmith
2023-09-21  3:49   ` G. Branden Robinson
2023-09-19 23:43 ` Adam Thornton
2023-09-20 13:23   ` Chet Ramey
2023-09-20 14:12     ` Alejandro Colomar (man-pages)
2023-09-19 23:47 ` KenUnix
2023-09-20  6:16 ` Jeremy C. Reed
2023-09-20  7:19   ` markus schnalke
2023-09-21 15:53 ` Kenneth Goodwin

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='weAmWI7k80Qmj5XlXCD5q39caw_2lYfi3Yn-_o3tkOCkisxnzHsgQawVkF3SbMqHk4WNSbc8cOdtUXUS5vWMBefNaJE_fwtRYDgmbY2QGqA=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=athornton@gmail.com \
    --cc=segaloco@protonmail.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).