From: Cág <ca6c@bitmessage.ch>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Lions book (not Origin of the name 'strategy'
Date: Wed, 09 Jan 2019 17:09:54 -0600 [thread overview]
Message-ID: <50b7d5e86dd89af2ab328f4038cb6ede@bitmessage.ch> (raw)
In-Reply-To: <20190109151243.71EA7156E410@mail.bitblocks.com>
Bakul Shah wrote:
>> I no longer have my Lions books on me, sadly enough (lost in a house
>> move)
>> but there certainly were some peculiar names in the kernel...
> https://github.com/kanner/lions-book
Something to be printed and read once again.
I remember I had a couple of handmade copies of bwk's C tutorial from
'74,
printed from the converted to LaTeX documents...
--
caóc
prev parent reply other threads:[~2019-01-09 23:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 5:42 [TUHS] " Dave Horsfall
2019-01-09 12:02 ` Dan Cross
2019-01-09 15:12 ` [TUHS] Lions book (not " Bakul Shah
2019-01-09 16:09 ` Warner Losh
2019-01-09 16:20 ` Clem Cole
2019-01-09 16:50 ` Warner Losh
2019-01-09 22:53 ` Dave Horsfall
2019-01-09 17:50 ` Bakul Shah
2019-01-09 17:55 ` Warner Losh
2019-01-09 17:20 ` Andy Kosela
2019-01-09 22:24 ` Dave Horsfall
2019-01-09 23:09 ` Cág [this message]
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=50b7d5e86dd89af2ab328f4038cb6ede@bitmessage.ch \
--to=ca6c@bitmessage.ch \
--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).