From: cym224@gmail.com (Nemo)
Subject: [TUHS] What sparked lint? [Was: Unix stories]
Date: Wed, 4 Jan 2017 20:30:48 -0500 [thread overview]
Message-ID: <CAJfiPzz-HegJOtjo524tusOhsu5LP2MTVGWBBM=nZbhHgpOB-g@mail.gmail.com> (raw)
On 4 January 2017 at 13:51, Steve Johnson <scj at yaccman.com> wrote (in part):
> These rules provided rich fodder for Lint, when it came along, [...]
All this lint talk caused me to reread your Lint article but no
history there. Was there a specific incident that begat lint?
N.
next reply other threads:[~2017-01-05 1:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 1:30 Nemo [this message]
2017-01-05 1:39 ` Larry McVoy
2017-01-05 3:20 ` Steve Johnson
2017-01-05 17:46 ` Ron Natalie
2017-01-05 20:55 ` Mary Ann Horton
2017-01-05 21:06 ` Clem Cole
2017-01-05 21:17 ` Chet Ramey
2017-01-05 21:30 ` Clem Cole
2017-01-05 21:42 ` ron minnich
2017-01-05 21:51 ` Ron Natalie
2017-01-05 22:02 ` Chet Ramey
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='CAJfiPzz-HegJOtjo524tusOhsu5LP2MTVGWBBM=nZbhHgpOB-g@mail.gmail.com' \
--to=cym224@gmail.com \
/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).