From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] TUHS Digest, Vol 33, Issue 5
Date: Mon, 6 Aug 2018 13:22:54 -0400 (EDT) [thread overview]
Message-ID: <20180806172254.340F618C09A@mercury.lcs.mit.edu> (raw)
> From: Bakul Shah
> What counts as a "formal spec"?
If you aren't familiar with the work in the field (it's been going on long
enough, it was around when I was an undergrad), some of the earlier messages
in the thread, e.g.:
https://minnie.tuhs.org//pipermail/tuhs/2018-August/014365.html
might provide some thing you could follow. (I'm not into that stuff, so I
point you in the right direction.)
Noel
next reply other threads:[~2018-08-06 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 17:22 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-06 17:26 Noel Chiappa
2018-08-06 13:06 Noel Chiappa
2018-08-06 15:52 ` Bakul Shah
2018-08-06 16:30 ` Hellwig Geisse
2018-08-06 21:19 ` Steve Johnson
[not found] <mailman.1.1533520802.6258.tuhs@minnie.tuhs.org>
2018-08-06 10:50 ` Steve Simon
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=20180806172254.340F618C09A@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).