From: clemc at ccc.com (Clem Cole)
Subject: [COFF] Fwd: Old and Tradition was [TUHS] V9 shell
Date: Wed, 12 Feb 2020 13:13:03 -0500 [thread overview]
Message-ID: <CAC20D2MZU0WD7L3GE0sgFiNK5crmbh=3Qe3TRvVOOs623MoOfg@mail.gmail.com> (raw)
In-Reply-To: <20200212162820.3A3BC18C0B6@mercury.lcs.mit.edu>
Sorry about that.
On Wed, Feb 12, 2020 at 11:45 AM Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
> > From: Clem Cole
>
> > Noel's email has much wisdom. New is not necessarily better and old
> > fashioned is not always a bad thing.
>
> For those confused by the reference, it's to an email that didn't go to the
> whole list (I was not sure if people would be interested):
>
> >> One of my favourite sayings (original source unknown; I saw it in
> >> "Shockwave Rider"): "There are two kinds of fool. One says 'This is
> >> old, and therefore good'; the other says 'This is new, and therefore
> >> better'."
>
> Noel
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200212/6c3c9be7/attachment.html>
next prev parent reply other threads:[~2020-02-12 18:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 16:28 jnc
2020-02-12 18:13 ` clemc [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-11 18:41 [COFF] " clemc
[not found] ` <CAP2nic2C4-m_Epcx7rbW2ssbS850ZFiLKiL+hg1Wxbcwoaa1vQ@mail.gmail.com>
2020-02-12 0:57 ` [COFF] Fwd: " athornton
2020-02-12 1:58 ` clemc
2020-02-12 3:01 ` lm
2020-02-12 18:12 ` clemc
2020-02-12 21:55 ` cym224
2020-02-12 22:11 ` imp
2020-02-12 22:45 ` sauer
2020-02-12 23:05 ` lm
2020-02-13 6:57 ` peter
2020-02-16 21:47 ` wobblygong
2020-02-16 22:10 ` clemc
2020-02-16 22:45 ` krewat
2020-02-16 23:50 ` bakul
2020-02-18 0:17 ` dave
2020-02-18 12:48 ` jpl.jpl
2020-02-24 9:40 ` ik
2020-02-24 15:19 ` lm
2020-02-24 16:27 ` clemc
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='CAC20D2MZU0WD7L3GE0sgFiNK5crmbh=3Qe3TRvVOOs623MoOfg@mail.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).