From: wkt at tuhs.org (Warren Toomey)
Subject: [COFF] [TUHS] Tech Sq elevator [ really type-checking ]
Date: Mon, 13 Jan 2020 10:49:12 +1000 [thread overview]
Message-ID: <20200113004912.GA27610@minnie.tuhs.org> (raw)
In-Reply-To: <202001130044.00D0ilcV616661@darkstar.fourwinds.com>
All, can we move this not-really-Unix discussion to COFF?
Thanks, Warren
P.S A bit more self-regulation too, please. You shouldn't need me to point
out when the topic has drifted so far :-)
next parent reply other threads:[~2020-01-13 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202001122225.00CMPc9S085970@tahoe.cs.Dartmouth.EDU>
[not found] ` <CAK7dMtBHfc35vb+5XP6WcBXDKsFyMxFSZ8vfgen7_5jgrnNxnQ@mail.gmail.com>
[not found] ` <202001122340.00CNeef0604557@darkstar.fourwinds.com>
[not found] ` <AB452025-FCE9-4D41-992A-D3135683A6D6@bitblocks.com>
[not found] ` <202001130044.00D0ilcV616661@darkstar.fourwinds.com>
2020-01-13 0:49 ` wkt [this message]
2020-01-13 1:23 ` crossd
2020-01-13 1:41 ` bakul
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=20200113004912.GA27610@minnie.tuhs.org \
--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).