From: athornton at gmail.com (Adam Thornton)
Subject: [COFF] Holy Wars of Computing
Date: Thu, 4 Feb 2021 08:39:01 -0700 [thread overview]
Message-ID: <9843D646-BED5-47AE-9FFB-CEFB534EED25@gmail.com> (raw)
In-Reply-To: <CAFZukdTDg4mKYf=TqDFqFm7sqsW-rgPTB8pD-VjQgMaENR_fwA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
> On Feb 4, 2021, at 1:41 AM, josh <joshnatis0 at gmail.com> wrote:
>
> To explain what I mean, take for example, The Tcl War <https://vanderburg.org/old_pages/Tcl/war/>. Other examples:
Peter da Silva. Now there’s a name I’ve not heard in a long time.
Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20210204/480b6381/attachment-0001.htm>
next prev parent reply other threads:[~2021-02-04 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 8:41 joshnatis0
2021-02-04 9:21 ` dave
2021-02-04 9:23 ` lars
2021-02-04 15:39 ` athornton [this message]
2021-02-04 17:34 ` lm
2021-02-04 18:11 ` athornton
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=9843D646-BED5-47AE-9FFB-CEFB534EED25@gmail.com \
--to=coff@minnie.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).