From: Derek Fawcus <dfawcus+lists-tuhs@employees.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Documentation for Unix 4.0
Date: Thu, 9 Jun 2022 23:19:22 +0100 [thread overview]
Message-ID: <YqJx6uyDskfM5wT1@clarinet.employees.org> (raw)
In-Reply-To: <20220607193233.3qh2lu3hzpa42zcj@illithid>
On Tue, Jun 07, 2022 at 02:32:33PM -0500, G. Branden Robinson wrote:
>
> By that addendum do you mean the "Recent Changes to C" 1-page memo dated
> 1978-11-15 that appears with some copies of Seventh Edition Unix
> documentation?
>
> For those who don't have it handy, it documents structure assignment and
> introduces enum types.
>
> Or is there another piece of samizdat I should keep an eye out for? :)
Have a look here: https://www.bell-labs.com/usr/dmr/www/cchanges.pdf
DF
next prev parent reply other threads:[~2022-06-09 22:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 1:40 [TUHS] " Warren Toomey via TUHS
2022-06-06 2:15 ` [TUHS] " Warner Losh
2022-06-06 9:19 ` arnold
2022-06-06 2:26 ` Larry McVoy
2022-06-06 9:20 ` arnold
2022-06-07 16:57 ` John Cowan
2022-06-07 19:32 ` G. Branden Robinson
2022-06-09 22:19 ` Derek Fawcus [this message]
2022-06-06 6:21 ` G. Branden Robinson
2022-06-06 9:26 ` arnold
2022-06-10 6:47 ` Ed Bradford
2022-06-10 7:31 ` [TUHS] Source code for SCCS (was Re: Re: Documentation for Unix 4.0) arnold
2022-06-10 8:38 ` [TUHS] " Matthias Bruestle
2022-06-10 10:03 ` arnold
2022-06-15 5:32 ` Stuart Remphrey
2022-06-10 14:22 ` [TUHS] Re: Documentation for Unix 4.0 Clem Cole
2022-06-10 19:24 ` John Cowan
2022-06-11 4:34 ` Ed Bradford
2022-06-11 14:43 ` Clem Cole
2022-06-12 5:45 ` Ed Bradford
2022-06-12 6:41 ` Warren Toomey via TUHS
2022-06-13 13:18 ` Jay Logue via TUHS
2022-06-13 15:49 ` Norman Wilson
2022-06-13 16:39 ` Michael Kjörling
2022-06-15 1:53 ` Stuart Remphrey
2022-06-15 5:57 ` Michael Kjörling
2022-06-15 12:04 ` Dan Cross
2022-06-16 7:45 ` Tom Ivar Helbekkmo via TUHS
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=YqJx6uyDskfM5wT1@clarinet.employees.org \
--to=dfawcus+lists-tuhs@employees.org \
--cc=tuhs@tuhs.org \
/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).