From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: "John Gilmore" <gnu@toad.com>
Cc: tuhs@tuhs.org, jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] History of popularity of C (GCC/Cygnus)
Date: Sat, 23 May 2020 06:33:07 +0200 [thread overview]
Message-ID: <5ef1f056cf19b3c157fc3a8f769b4494@firemail.de> (raw)
In-Reply-To: <28538.1590179965@hop.toad.com>
>Early on, GCC had the slight advantage that because it was free (as in
>both beer and speech) and had an email community of maintainers
I remember that we started moving to gcc, gmake, etc,, because these tools
performed simply spoken better than the native SNI ones.
next prev parent reply other threads:[~2020-05-23 4:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 18:28 [TUHS] History of popularity of C Noel Chiappa
2020-05-21 18:44 ` Thomas Paulsen
2020-05-21 19:06 ` Paul Winalski
2020-05-21 20:27 ` Thomas Paulsen
2020-05-22 8:52 ` Tom Ivar Helbekkmo via TUHS
2020-05-22 9:51 ` Tyler Adams
2020-05-22 11:09 ` arnold
2020-05-22 11:15 ` Tyler Adams
2020-05-22 18:40 ` John Gilmore
2020-05-22 19:01 ` Toby Thain
2020-05-22 19:35 ` Larry McVoy
2020-05-22 19:31 ` Larry McVoy
2020-05-22 20:19 ` Michael Kjörling
2020-05-22 14:59 ` Toby Thain
2020-05-22 20:39 ` [TUHS] History of popularity of C (GCC/Cygnus) John Gilmore
2020-05-23 4:33 ` Thomas Paulsen [this message]
2020-05-22 11:58 ` [TUHS] History of popularity of C A. P. Garcia
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=5ef1f056cf19b3c157fc3a8f769b4494@firemail.de \
--to=thomas.paulsen@firemail.de \
--cc=gnu@toad.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).